https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99654
Marek Polacek changed:
What|Removed |Added
Last reconfirmed||2021-03-30
Status|UNCONFIRME
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99654
--- Comment #4 from Frank Ch. Eigler ---
A quick diff between the two -fverbose-asm dumps confirms that the generated
object code is identical with or without the -gno-as-locview-support, but the
DW_AT_entry_pc differs.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99654
--- Comment #3 from Will Cohen ---
Created attachment 50480
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50480&action=edit
Default assembly code generated by compiler
Default Assembly generated by compiler to compare to the
-gno-as-locvi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99654
--- Comment #2 from Will Cohen ---
Created attachment 50479
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50479&action=edit
assembly file compiled with -gno-as-locview-support
Resulting assembly language file generated by:
gcc -O3 -g -gn
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99654
--- Comment #1 from Will Cohen ---
Jan Kratochvil at Red Hat mentioned that the DW_AT_entry_pc values looked
reasonable when -gno-as-locview-support was added to the command line. I
checked and they do look more reasonable. Does this mean an i
