https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70082
--- Comment #7 from Carlos O'Donell ---
(In reply to Martin Sebor from comment #6)
> Carlos, do you still feel diagnosing some of the [mis]uses would be helpful,
> e.g., by a warning? (I ask because I've been doing some work in this area
> --
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70082
Martin Sebor changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70082
--- Comment #5 from Carlos O'Donell ---
Would it be a better solution to:
(a) Fix PLT initialization on arm and ppc64 (allows some function calls to be
made).
(b) Document safe functions in glibc manual.
(c) Have gcc manual reference glibc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70082
--- Comment #4 from Carlos O'Donell ---
(In reply to Jakub Jelinek from comment #3)
> I don't think the compiler should do the policeman here, it is enough if
> glibc documents what it does and doesn't support in ifunc (which is of
> course
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70082
--- Comment #3 from Jakub Jelinek ---
I don't think the compiler should do the policeman here, it is enough if glibc
documents what it does and doesn't support in ifunc (which is of course
generally arch dependent, it really depends on if you
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70082
--- Comment #2 from Carlos O'Donell ---
There might be the case where it is argued that documentation is all that is
needed, but that doesn't yield a robust implementation. My biggest worry after
seeing gperftools/tcmalloc use IFUNC is that it
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70082
--- Comment #1 from Carlos O'Donell ---
... and non-local variable access should be disallowed, as well as TLS
variables, and anything that needs a constructor to be initialized (non-POD).
