https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63215
--- Comment #6 from Richard Biener rguenth at gcc dot gnu.org ---
(In reply to Jan Hubicka from comment #5)
Hmm, we can easily distinguish them by seeing whether a definition is
available.
Well, what happens in this testcase is that we see
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63215
Jan Hubicka hubicka at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63215
--- Comment #2 from Jan Hubicka hubicka at gcc dot gnu.org ---
As an ugly workaround, marking them __attribute__ ((externally_visible, used))
should work. They will however be added into every binary that is linked with
them no mater if they are
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63215
--- Comment #3 from Patrick Oppenlander patrick at motec dot com.au ---
Thanks for the information!
Is there a list of these functions somewhere?
Is this somehow related to bug 60395?
Thanks,
Patrick
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63215
--- Comment #4 from Richard Biener rguenth at gcc dot gnu.org ---
Hmm, we can easily distinguish them by seeing whether a definition is
available.
That is, symbols with a definition should _always_ be output? I don't see
any difficulties with
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63215
--- Comment #5 from Jan Hubicka hubicka at ucw dot cz ---
Hmm, we can easily distinguish them by seeing whether a definition is
available.
Well, what happens in this testcase is that we see ABS at LTO time, we promote
it to static (because no
