https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116245
--- Comment #7 from Stefan Schulze Frielinghaus
---
I gave it a quick try on s390 and test passes, now. Thanks!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116245
Jakub Jelinek changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116245
--- Comment #5 from GCC Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:df4062c54b0b3c5f5c6a1f1a2454abf965100e3a
commit r15-2753-gdf4062c54b0b3c5f5c6a1f1a2454abf965100e3a
Author: Jakub Jelinek
Date: T
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116245
Jakub Jelinek changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
Eve
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116245
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116245
--- Comment #3 from Stefan Schulze Frielinghaus
---
Thanks for the ping. The test is skipped for -m31 and fails for -m64. Maybe
this is some sort of endianness thingy?
typedef __attribute__((__vector_size__ (64))) unsigned __int128 VV;
__at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116245
Richard Biener changed:
What|Removed |Added
Target||s390x
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116245
--- Comment #2 from Andrew Pinski ---
(In reply to Sam James from comment #1)
> oh, it only fails for -m31 (s390)...
__int128 should not be supported there ...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116245
--- Comment #1 from Sam James ---
oh, it only fails for -m31 (s390)...