https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88332
seurer at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88332
--- Comment #11 from pkoning at gcc dot gnu.org ---
Thanks, I had forgotten.
Seurer, could you update to r265741 or later and check if that cures the issue?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88332
--- Comment #10 from Segher Boessenkool ---
You have
/* { dg-error "alignment of 's' is greater" "" { target pdp11*-*-* } } */
(the "" was added in r265741, the source tree I looked at wasn't up-to-date).
dg.exp says this is
# dg-error regexp
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88332
--- Comment #9 from pkoning at gcc dot gnu.org ---
Comment? I thought the comment is the null string after the regexp to match.
Should it read { target { pdp11-*-* } } with the extra braces?
Other examples show up both with the braces and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88332
--- Comment #8 from Segher Boessenkool ---
"target pdp11*-*-*" is the _comment_ argument to dg-error here as written;
that's why it is displayed in the summary like that, too. I don't see why
it doesn't fail on most systems though, hrm.
FWIW,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88332
--- Comment #7 from seurer at gcc dot gnu.org ---
The original machine I saw the failure on was a power8 BE machine running RHEL
7.6 but gcc110 is:
seurer@gcc1-power7:~$ lscpu
Architecture: ppc64
CPU op-mode(s):32-bit, 64-bit
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88332
--- Comment #6 from seurer at gcc dot gnu.org ---
I tried it on the BE powerpc64 machine in the gcc compiler farm,
gcc110.fsffrance.org, and the same thing happens.
seurer@gcc1-power7:~/gcc/build/gcc-test$ ~/gcc/install/gcc-test/bin/gcc -v
Using
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88332
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |9.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88332
--- Comment #5 from pkoning at gcc dot gnu.org ---
Could you post the full config specification and what the build system is? It
seems hard to reproduce, and it is rather puzzling for a powerpc build to
trigger a check that is explicitly there
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88332
Martin Sebor changed:
What|Removed |Added
CC||msebor at gcc dot gnu.org
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88332
pkoning at gcc dot gnu.org changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |pkoning at gcc dot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88332
--- Comment #2 from seurer at gcc dot gnu.org ---
powerpc64 for sure BE and possibly LE.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88332
--- Comment #1 from pkoning at gcc dot gnu.org ---
What is your target? I checked this on linux-x86_64 (native build). I don't
see the complaint about line 15 in that run.
13 matches
Mail list logo
