[Bug debug/46724] [4.6 Regression] Wrong debug info: Invalid variable location

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46724 --- Comment #13 from Alexandre Oliva 2011-01-19 22:00:09 UTC --- Author: aoliva Date: Wed Jan 19 22:00:00 2011 New Revision: 169034 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=169034 Log: PR debug/47079 PR debug/46724 * function.c (ins

[Bug debug/46724] [4.6 Regression] Wrong debug info: Invalid variable location

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46724 Alexandre Oliva changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

[Bug debug/46724] [4.6 Regression] Wrong debug info: Invalid variable location

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46724 --- Comment #11 from Alexandre Oliva 2010-12-22 03:49:06 UTC --- Author: aoliva Date: Wed Dec 22 03:49:00 2010 New Revision: 168160 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=168160 Log: PR debug/46724 * function.c (assign_parms_augme

[Bug debug/46724] [4.6 Regression] Wrong debug info: Invalid variable location

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46724 Alexandre Oliva changed: What|Removed |Added Attachment #22806|0 |1 is obsolete|

[Bug debug/46724] [4.6 Regression] Wrong debug info: Invalid variable location

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46724 Alexandre Oliva changed: What|Removed |Added Attachment #22792|0 |1 is obsolete|

[Bug debug/46724] [4.6 Regression] Wrong debug info: Invalid variable location

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46724 --- Comment #8 from Jakub Jelinek 2010-12-17 09:44:03 UTC --- Created attachment 22794 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=22794 gcc46-pr46724-incremental.patch Incremental patch for that. BTW, the reason why a location list is

[Bug debug/46724] [4.6 Regression] Wrong debug info: Invalid variable location

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46724 --- Comment #7 from Jakub Jelinek 2010-12-17 08:55:06 UTC --- Ah, the trick is that you keep the artificial PARM_DECL out of DECL_ARGUMENTS as it was and manually add it in var-tracking. To avoid dropping the DECL_NAME test you could perhaps give

[Bug debug/46724] [4.6 Regression] Wrong debug info: Invalid variable location

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46724 --- Comment #6 from Alexandre Oliva 2010-12-17 06:19:30 UTC --- Created attachment 22792 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=22792 Patch I'm testing that fixes the bug Here's what I meant. It does fix the bug at hand, and (surpr

[Bug debug/46724] [4.6 Regression] Wrong debug info: Invalid variable location

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46724 Alexandre Oliva changed: What|Removed |Added AssignedTo|unassigned at gcc dot |aoliva at gcc dot gnu.org

[Bug debug/46724] [4.6 Regression] Wrong debug info: Invalid variable location

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46724 --- Comment #4 from Alexandre Oliva 2010-12-16 05:38:44 UTC --- Considering that we create a decl for the implicit argument that holds the address of , perhaps the best approach would be to emit debug info for that artificial decl. The initial i

[Bug debug/46724] [4.6 Regression] Wrong debug info: Invalid variable location

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46724 Jakub Jelinek changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug debug/46724] [4.6 Regression] Wrong debug info: Invalid variable location

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46724 --- Comment #2 from Andreas Krebbel 2010-12-02 09:51:17 UTC --- Marked as 4.6 regression. The behavior of 4.5.2 isn't helpful either but it doesn't return a wrong value as with 4.6.