https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82630
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82630
--- Comment #7 from Jakub Jelinek ---
Author: jakub
Date: Mon Oct 23 20:39:59 2017
New Revision: 254025
URL: https://gcc.gnu.org/viewcvs?rev=254025=gcc=rev
Log:
PR debug/82630
* target.def (const_not_ok_for_debug_p): Default to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82630
--- Comment #6 from Rafael Avila de Espindola ---
(In reply to H.J. Lu from comment #3)
> (In reply to Jakub Jelinek from comment #2)
> > The problem is the assembler's special treatment of _GLOBAL_OFFSET_TABLE_,
> > that
> > .long
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82630
Jakub Jelinek changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82630
--- Comment #4 from Jakub Jelinek ---
Then it would be unclear what that generates (something with the old assembler,
something else with the new assembler).
Trying now to change gcc so that it actually doesn't delegitimize UNSPEC_GOTOFF
in this
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82630
--- Comment #3 from H.J. Lu ---
(In reply to Jakub Jelinek from comment #2)
> The problem is the assembler's special treatment of _GLOBAL_OFFSET_TABLE_,
> that
> .long _GLOBAL_OFFSET_TABLE_ or .quad _GLOBAL_OFFSET_TABLE_ on x86 doesn't
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82630
Jakub Jelinek changed:
What|Removed |Added
CC||hjl.tools at gmail dot com,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82630
--- Comment #1 from Richard Biener ---
*** Bug 82631 has been marked as a duplicate of this bug. ***
