https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88920
Bill Schmidt <wschmidt at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |---
--- Comment #15 from Bill Schmidt <wschmidt at gcc dot gnu.org> ---
I don't consider this issue resolved.
Yesterday I did a make-check for a single test case, using
RUNTESTFLAGS="powerpc.exp=srad-modulo.c". It failed, so I looked in my log
file and saw:
spawn -ignore SIGHUP /home/wschmidt/gcc/build/gcc-mainline-test2/gcc/xgcc
-B/home/wschmidt/gcc/build/gcc-mainline-test2/gcc/
/home/wschmidt/gcc/gcc-mainline-test2/gcc/testsuite/gcc.target/powerpc/srad-modulo.c
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -O2 -mvsx -lm -o ./srad-modulo.exe^M
^[[01m^[[Kcc1:^[[m^[[K ^[[01;31m^[[Kerror: ^[[m^[[Kargument to
'^[[01m^[[K-O^[[m^[[K' should be a non-negative integer, '^[[01m^[[Kg^[[m^[[K',
'^[[01m^[[Ks^[[m^[[K' or '^[[01m^[[Kfast^[[m^[[K'^M
compiler exited with status 1
Executing on host: /home/wschmidt/gcc/build/gcc-mainline-test2/gcc/xgcc
-B/home/wschmidt/gcc/build/gcc-mainline-test2/gcc/ offload_gcn7262.c
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -foffload=amdgcn-unknown-amdhsa -S -o
offload_gcn7262.s (timeout = 300)
spawn -ignore SIGHUP /home/wschmidt/gcc/build/gcc-mainline-test2/gcc/xgcc
-B/home/wschmidt/gcc/build/gcc-mainline-test2/gcc/ offload_gcn7262.c
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -foffload=amdgcn-unknown-amdhsa -S -o
offload_gcn7262.s^M
xgcc: fatal error: GCC is not configured to support amdgcn-unknown-amdhsa as
offload target^M
compilation terminated.^M
compiler exited with status 1
FAIL: gcc.target/powerpc/srad-modulo.c (test for excess errors)
Excess errors:
^[[01m^[[Kcc1:^[[m^[[K ^[[01;31m^[[Kerror: ^[[m^[[Kargument to
'^[[01m^[[K-O^[[m^[[K' should be a non-negative integer, '^[[01m^[[Kg^[[m^[[K',
'^[[01m^[[Ks^[[m^[[K' or '^[[01m^[[Kfast^[[m^[[K'
I was really confused by this (granted, the embedded color codes didn't help),
and if I hadn't already been aware of this bugzilla I wouldn't have known what
to think. I was able to correct my error, but the existence of this bug wasted
my time and would really have flummoxed anyone who hadn't seen the bug before.
I don't think this should be closed until the problem is resolved when we don't
configure offload targets. "Just once" is better than 420 times, but it's
still wrong.
