https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95574
Alexandre Oliva <aoliva at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |aoliva at gcc dot gnu.org
--- Comment #9 from Alexandre Oliva <aoliva at gcc dot gnu.org> ---
A noreturn function may raise an exception, and var tracking notes from the
call would be relevant within the exception handler. Arguably, issuing a .loc
just before end of sequence, because of such tracking notes, is poor practice.
However, the possibility of zero-sized padding, asm notes, etc, makes
eliminating such possibilities altogether extremely tricky, with forced padding
as a likely result of mandatory compliance with this rule. IMHO relaxing the
rule makes more sense.
Location views and presumed-return-address notes change the notion that and end
of sequence can't have other information associated with it. Location views
even change the notion that there's a single row per address, unless you
conceive of them as a fractional part of the address, which would then cause
the end of sequence opcode to bump (increment or reset) the view, thus getting
a distinct address, at least in the fractional part.
