http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51695
--- Comment #6 from Jakub Jelinek 2012-01-04
19:58:07 UTC ---
Author: jakub
Date: Wed Jan 4 19:58:03 2012
New Revision: 182886
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=182886
Log:
PR debug/51695
* dwarf2out.c (output_loc_li
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51695
--- Comment #5 from Jan Kratochvil
2012-01-04 14:20:29 UTC ---
(In reply to comment #4)
> they could have unwanted
> side-effects (reading uninitialized memory, division by zero, producing NaNs
> etc.) that the debugger might complain about loudl
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51695
Richard Guenther changed:
What|Removed |Added
Priority|P3 |P1
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51695
Jakub Jelinek changed:
What|Removed |Added
CC||jan.kratochvil at redhat
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51695
--- Comment #3 from Jakub Jelinek 2012-01-04
11:04:41 UTC ---
We can always work around this as in (completely untested):
--- gcc/dwarf2out.c2012-01-03 16:22:48.794866121 +0100
+++ gcc/dwarf2out.c2012-01-04 11:50:30.516022278 +0100
@@ -8
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51695
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51695
--- Comment #1 from Jakub Jelinek 2011-12-28
11:35:23 UTC ---
The NOTE_INSN_VAR_LOCATION argument for variable o is extremely huge in this
case and we hit the 64KB limit on .debug_loc expressions.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51695
Jakub Jelinek changed:
What|Removed |Added
Component|tree-optimization |debug
Target Milestone|---
