https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62225
Eric Botcazou changed:
What|Removed |Added
CC||ebotcazou at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62225
--- Comment #5 from Sandra Loosemore ---
Thinking about this some more
Why doesn't -g always enable -fvar-tracking by default? It's currently only
enabled if you specify both -g and -O.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62225
Sandra Loosemore changed:
What|Removed |Added
CC||sandra at codesourcery dot com
--- Co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62225
--- Comment #3 from Yao Qi ---
(In reply to Andrew Pinski from comment #1)
> I bet if you remove register, it will work. Or compile with variable
> tracking turned on.
I compiled the code again with -fvar-tracking, and looks DW_AT_location for
l
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62225
--- Comment #2 from Yao Qi ---
arm-none-eabi gcc mainline (4.10.0 20140818) and 4.9.2 has this problem too.
The test case is compiled with -mthumb flag.
<1><71>: Abbrev Number: 6 (DW_TAG_subprogram)
<72> DW_AT_external: 1
<72> D
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62225
--- Comment #1 from Andrew Pinski ---
I bet if you remove register, it will work. Or compile with variable tracking
turned on.
