https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78857
stli at linux dot vnet.ibm.com changed:
What|Removed |Added
Status|RESOLVED|VERIFIED
--- Comment
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: stli at linux dot vnet.ibm.com
CC: krebbel at gcc dot gnu.org
Target Milestone: ---
Target: S390
For s390, I am now using the c11 atomic builtins in glibc
: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: stli at linux dot vnet.ibm.com
Target Milestone: ---
Target: S390
On s390, a comparison of e.g. a
erity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: stli at linux dot vnet.ibm.com
Target Milestone: ---
The C comparison operators <, >, <=, >= (as opposed to the isgreater, etc.
macros) are speci
: normal
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: stli at linux dot vnet.ibm.com
Target Milestone: ---
Starting with glibc-commits "Add configure check to test if gcc supports
attribute ifunc."
(https://sour
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66303
--- Comment #12 from stli at linux dot vnet.ibm.com ---
The glibc bug https://sourceware.org/bugzilla/show_bug.cgi?id=18508
is fixed upstream with commit
https://sourceware.org/git/?p=glibc.git;a=commit;h=890b7a4b33d482b5c768ab47d70758b80227e9bc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66303
stli at linux dot vnet.ibm.com changed:
What|Removed |Added
CC||stli at linux dot
