https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93419
Martin Sebor changed:
What|Removed |Added
Assignee|msebor at gcc dot gnu.org |unassigned at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93419
Richard Biener changed:
What|Removed |Added
Status|NEW |ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93419
Martin Sebor changed:
What|Removed |Added
Keywords||rejects-valid
Target|hurd fre
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93419
Martin Sebor changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93419
--- Comment #5 from kloetzl ---
Sorry for missing out the details, here goes:
I work in a Debian Hurd 20290705 image using qemu. The example file is given
above. Compiling with `gcc -Wall -Wextra ifunc.c` produces the following error.
error: i
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93419
Martin Sebor changed:
What|Removed |Added
CC||msebor at gcc dot gnu.org
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93419
--- Comment #3 from kloetzl ---
Hm, I feared that this would be the answer I would get. This makes GCCs
__has_attribute much less useful than Clangs version where the docs state:
“This function-like macro takes a single identifier argument that
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93419
--- Comment #2 from Andrew Pinski ---
I think the docs are clear here too:
The special operator __has_attribute (operand) may be used in ‘#if’ and ‘#elif’
expressions to test whether the attribute referenced by its operand is
recognized by GCC.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93419
--- Comment #1 from Andrew Pinski ---
__has_attribute(ifunc) is true as the attribute is supported all the way
through the compiler up to the point where it gets emitted.
Really __has_attribute is a bad execuse for not doing proper feature testi
