https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67417
Alan Modra changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67417
--- Comment #6 from Alan Modra ---
Author: amodra
Date: Tue Sep 1 23:25:48 2015
New Revision: 227389
URL: https://gcc.gnu.org/viewcvs?rev=227389&root=gcc&view=rev
Log:
[RS6000] Weak functions may not be file local
A weak symbol defined in the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67417
--- Comment #5 from Alan Modra ---
Author: amodra
Date: Tue Sep 1 23:04:58 2015
New Revision: 227387
URL: https://gcc.gnu.org/viewcvs?rev=227387&root=gcc&view=rev
Log:
[RS6000] Weak functions may not be file local
A weak symbol defined in the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67417
--- Comment #4 from Alan Modra ---
Author: amodra
Date: Tue Sep 1 23:03:19 2015
New Revision: 227386
URL: https://gcc.gnu.org/viewcvs?rev=227386&root=gcc&view=rev
Log:
[RS6000] Weak functions may not be file local
A weak symbol defined in the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67417
--- Comment #3 from Alan Modra ---
Yes, exactly. When a COMDAT group in another file is chosen, the rs6000
predicate current_file_function_operand gets the wrong answer. COMDAT group
functions use weak symbols, and weak symbols more generally h
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67417
--- Comment #2 from Richard Biener ---
This is simply an inline class method which should be in a COMDAT section.
The linker is free to pick either.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67417
--- Comment #1 from Alan Modra ---
BTW, the linker error message doesn't identify the correct function, which is
looking like a linker bug.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67417
Alan Modra changed:
What|Removed |Added
Target||powerpc64-linux
Status|UNCONFIR
