Maciej W. Rozycki wrote:
On Tue, 26 May 2020, Rob Savoye wrote:
I'll run some RISC-V remote GCC/GDB testing and compare results for
DejaGnu 1.6/1.6.1 vs trunk. It will take several days though, as it takes
many hours to go through these testsuite runs.
That'd be great. I'd rather push out a stable release, than have to
fix bugs right after it gets released.
I have completed GCC and GDB testing now with the `riscv64-linux-gnu'
target and the `x86_64-linux-gnu' host.
GDB results obtained with real hardware are looking good, with the usual
fluctuation due to intermittent failures caused by races in test cases:
[...]
Similarly GCC test results taken with QEMU in the user emulation mode
show a couple of intermittent discrepancies (not present on a rerun)
within the libgo testsuite only:
[...]
However native `x86_64-linux-gnu' GDB testing does not work at all; all
it gets is:
get_compiler_info: default_target_compile: No compiler to compile with
get_compiler_info: compiler_info not provided
get_compiler_info: got unexpected diagnostics
get_compiler_info: unknown
gdb compile failed, default_target_compile: No compiler to compile with
Conversely all things being equal DejaGnu 1.6 finds native `/usr/bin/gcc'
just fine:
get_compiler_info: set compiler_info "unknown"
get_compiler_info: set compiler_info [join {gcc 9 2 1} -]
get_compiler_info: gcc-9-2-1
and in the verbose mode also:
Checking /home/macro/bin for gcc
Checking /home/macro/bin for gcc
Checking /usr/local/bin for gcc
Checking /usr/bin for gcc
Choosing /usr/bin/gcc
I ran a quick bisection and the culprit turned out to be:
ba60272a5ac6f6a7012acca03f596a6ed003f044 is the first bad commit
commit ba60272a5ac6f6a7012acca03f596a6ed003f044
Author: Jacob Bachmeyer <jcb62281+...@gmail.com>
Date: Mon May 25 08:40:46 2020 -0600
Establish a default C compiler by evaluating [find_gcc] if no other
compiler is given.
So this regression has to be fixed before any new release is made.
I will look into this. So far, I have confirmed that the problem does
occur and that setting the "compiler" board_info key in
baseboards/unix.exp seems to avoid it. It looks like the default is not
being selected in all cases where it should be used. I still need to
find the exact problem to write a regression test to isolate this bug
and make it stay squashed. Please submit a bug report to
<bug-deja...@gnu.org> for this issue.
Side note to Rob: should I base the fix for this on the
"new-api-for-1.6.3" branch or should we have a merge commit for that
later? (Or should I go ahead and merge that branch now?)
-- Jacob
