[Bug testsuite/101002] Some powerpc tests fail with -mlong-double-64

2024-10-30 Thread bergner at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101002 --- Comment #11 from Peter Bergner --- (In reply to Segher Boessenkool from comment #9) > (In reply to Peter Bergner from comment #4) > > These die because the struct we're using to check the alignment of uses long > > double as the "big" aligne

[Bug testsuite/101002] Some powerpc tests fail with -mlong-double-64

2023-06-22 Thread dje at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101002 --- Comment #10 from David Edelsohn --- Please be careful about the effect on AIX. AIX defaults to long-double-64.

[Bug testsuite/101002] Some powerpc tests fail with -mlong-double-64

2023-06-21 Thread segher at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101002 --- Comment #9 from Segher Boessenkool --- (In reply to Peter Bergner from comment #4) > These die because the struct we're using to check the alignment of uses long > double as the "big" aligned type. We could either disable the tests using a

[Bug testsuite/101002] Some powerpc tests fail with -mlong-double-64

2023-06-21 Thread bergner at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101002 --- Comment #8 from Peter Bergner --- (In reply to Peter Bergner from comment #7) > There are a few other testsuite regressions due to a linker warning the > testsuite wouldn't ignore: > > /opt/binutils-power10/bin/ld: /tmp/ccysrhL7.o uses 64-b

[Bug testsuite/101002] Some powerpc tests fail with -mlong-double-64

2023-06-21 Thread bergner at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101002 --- Comment #7 from Peter Bergner --- (In reply to Peter Bergner from comment #6) > I'm going to test the following to see whether anything bad falls out: > > --- a/gcc/config/rs6000/rs6000-builtin.cc > +++ b/gcc/config/rs6000/rs6000-builtin.cc

[Bug testsuite/101002] Some powerpc tests fail with -mlong-double-64

2023-06-21 Thread bergner at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101002 --- Comment #6 from Peter Bergner --- (In reply to Peter Bergner from comment #5) > The creation of the __ibm128 type is guarded by: > > if (TARGET_LONG_DOUBLE_128 && (!TARGET_IEEEQUAD || TARGET_FLOAT128_TYPE)) > > Since the __ibm128 type is

[Bug testsuite/101002] Some powerpc tests fail with -mlong-double-64

2023-06-21 Thread bergner at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101002 --- Comment #5 from Peter Bergner --- (In reply to Peter Bergner from comment #4) > gcc.target/powerpc/pr85657-3.c > gcc.target/powerpc/signbit-1.c > pr85657-3.c:38:20: error: unknown type name ‘__ibm128’; did you mean > ‘__int128’? > > These d

[Bug testsuite/101002] Some powerpc tests fail with -mlong-double-64

2023-06-20 Thread bergner at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101002 Peter Bergner changed: What|Removed |Added CC||linkw at gcc dot gnu.org Ever confi

[Bug testsuite/101002] Some powerpc tests fail with -mlong-double-64

2021-06-11 Thread segher at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101002 --- Comment #3 from Segher Boessenkool --- (In reply to Segher Boessenkool from comment #2) > The first test is for _Float128. What goes wrong there? > > For all these tests yo ..u have to figure out what is going wrong. After that it will l

[Bug testsuite/101002] Some powerpc tests fail with -mlong-double-64

2021-06-11 Thread segher at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101002 --- Comment #2 from Segher Boessenkool --- The first test is for _Float128. What goes wrong there? For all these tests yo

[Bug testsuite/101002] Some powerpc tests fail with -mlong-double-64

2021-06-10 Thread bergner at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101002 --- Comment #1 from Peter Bergner --- Are these tests valid for long double == double? Ie, do we just need to disable them when using -mlong-double-64 or are these real bugs? I'm guessing the latter for most of these tests, but just checking.