https://sourceware.org/bugzilla/show_bug.cgi?id=29551
--- Comment #4 from Jan Beulich <jbeulich at suse dot com> --- If that also allows _GLOBAL_OFFSET_TABLE_-. to work as expected, perhaps that's the way to go. It's been a long time, but I expect that form of expression was what I had in mind when adding the check for BFD_RELOC_32_PCREL. What I'm unsure about is whether _GLOBAL_OFFSET_TABLE_@GOTPCREL is actually a legitimate construct. We're way to lax with (not) rejecting invalid <symbol>@<reloc> constructs anyway, so us not currently rejecting this means about nothing. -- You are receiving this mail because: You are on the CC list for the bug.