[Bug target/89626] Extraneous error message when compiling vector __int128

2021-05-04 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89626 Richard Biener changed: What|Removed |Added Status|NEW |ASSIGNED

[Bug target/89626] Extraneous error message when compiling vector __int128

2019-03-07 Thread segher at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89626 Segher Boessenkool changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug target/89626] Extraneous error message when compiling vector __int128

2019-03-07 Thread segher at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89626 --- Comment #10 from Segher Boessenkool --- But it behaves exactly likes this on LE ELFv2 systems as well. Only explicitly signed and unsigned types are documented, sure, but that does not make all that much sense, IMO.

[Bug target/89626] Extraneous error message when compiling vector __int128

2019-03-07 Thread wschmidt at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89626 --- Comment #9 from Bill Schmidt --- vector __int128 is equivalent to vector signed __int128, and only is defined for the ELFv2 ABI. Technically ELFv2 can be used anywhere, but in practice it is little-endian only.LE systems require a minimu

[Bug target/89626] Extraneous error message when compiling vector __int128

2019-03-07 Thread seurer at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89626 seurer at gcc dot gnu.org changed: What|Removed |Added CC||seurer at gcc dot gnu.org ---

[Bug target/89626] Extraneous error message when compiling vector __int128

2019-03-07 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89626 --- Comment #7 from Jakub Jelinek --- If vector followed by __int128 is unconditionally mapped to __vector, then so should vector double.

[Bug target/89626] Extraneous error message when compiling vector __int128

2019-03-07 Thread segher at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89626 --- Comment #6 from Segher Boessenkool --- "vector signed __int128" and "vector unsigned __int128" are both defined, and both work fine. But "vector __int128" is not defined in the ABI, and does not work unless you are building for power8 or up.

[Bug target/89626] Extraneous error message when compiling vector __int128

2019-03-07 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89626 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org --- Comment #5

[Bug target/89626] Extraneous error message when compiling vector __int128

2019-03-07 Thread segher at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89626 --- Comment #4 from Segher Boessenkool --- If you use -mcpu=power8 (or up) it works fine.

[Bug target/89626] Extraneous error message when compiling vector __int128

2019-03-07 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89626 --- Comment #3 from Andrew Pinski --- Looks like the preprocess conditional identifier does not recognize __int128 as something it should be used with vector. I doubt this is a real bug as vector __int128 is not defined in the PowerPC specificat

[Bug target/89626] Extraneous error message when compiling vector __int128

2019-03-07 Thread kelvin at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89626 kelvin at gcc dot gnu.org changed: What|Removed |Added CC||kelvin at gcc dot gnu.org,

[Bug target/89626] Extraneous error message when compiling vector __int128

2019-03-07 Thread kelvin at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89626 --- Comment #1 from kelvin at gcc dot gnu.org --- Created attachment 45923 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45923&action=edit preprocessed source code for reproducer