https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70957
Bill Schmidt changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70957
--- Comment #13 from Bill Schmidt ---
Author: wschmidt
Date: Fri Jun 3 13:18:25 2016
New Revision: 237067
URL: https://gcc.gnu.org/viewcvs?rev=237067=gcc=rev
Log:
2016-06-03 Bill Schmidt
PR target/70957
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70957
--- Comment #12 from Bill Schmidt ---
Author: wschmidt
Date: Fri Jun 3 13:14:26 2016
New Revision: 237066
URL: https://gcc.gnu.org/viewcvs?rev=237066=gcc=rev
Log:
2016-06-03 Bill Schmidt
PR target/70957
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70957
--- Comment #11 from Bill Schmidt ---
OK, I've traced this down to its sordid origins. The problem arises when the
test case is run on a machine using an old target assembler. If the assembler
doesn't support POWER8 instructions, this causes
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70957
Bill Schmidt changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|2016-05-06
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70957
--- Comment #9 from Bill Seurer ---
Systems where I see it fail:
granola
yavin3
Systems where I do not:
bns
All are power7 BE systems. I didn't do anything special on any of the systems.
I ran configure like this on all of them:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70957
--- Comment #8 from Bill Schmidt ---
Looks like it also did not fail in the latest gcc-testresults Power7 BE run.
Going to stop looking at this unless/until it shows up again.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70957
Bill Schmidt changed:
What|Removed |Added
Status|NEW |UNCONFIRMED
Ever confirmed|1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70957
--- Comment #6 from Bill Schmidt ---
The test also passed on P7 at the time I committed the patch.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70957
--- Comment #5 from Bill Schmidt ---
I applied the same patch to gcc-6-branch, and the test works correctly on a
Power7 machine. Thus we appear to be exposing a recent problem introduced on
trunk. I'll try to bisect this.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70957
--- Comment #4 from Bill Schmidt ---
The other odd thing is that we fail only on the signed and unsigned long long
cases, and all of the other variants work.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70957
--- Comment #3 from Bill Schmidt ---
Configuration for the two compilers used:
$GCC_SRC/configure --enable-__cxa_atexit
--enable-languages=c,c++,fortran,objc,obj-c++,go --with-cpu=power7
--disable-libsanitizer
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70957
Bill Schmidt changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70957
Bill Schmidt changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |wschmidt at gcc dot
gnu.org
---
14 matches
Mail list logo