Re: [PATCH 2/2] RISC-V: adjust logic to avoid register name symbols

[Jan Beulich <jbeulich@suse.com>]

On 15.02.2023 09:48, Nelson Chu wrote:
> Thanks for the detailed clarify :-)
> 
> A quick update, I just use riscv-gnu-toolchain to build a linux toolchain with,
> gcc (releases/gcc-12.2.0) + binutils (master + these two patches) +
> glibc (release/2.37/master),
> and then I get some unexpected errors from gcc testsuite, which won't
> occurred without these patches.
> 
>                ========= Summary of gcc testsuite =========
>                             | # of unexpected case / # of unique unexpected case
>                             |          gcc |          g++ |     gfortran |
>      rv64gc/  lp64d/ medlow |  347 /    62 |   29 /     9 |    0 /     0 |
> 
> I haven't tested the elf regressions, and the whole linux regression,
> but it seems that there are some unexpected situations that we have
> not considered in this patch.

Hmm, this suggests to me that testcases are missing in the gas testsuite.

> Reproduce commands,
> 1. git clone https://github.com/riscv-collab/riscv-gnu-toolchain.git --recursive
> 2. need to install some tools before build,
> https://github.com/riscv-collab/riscv-gnu-toolchain#prerequisites
> 3. git checkout branches of gcc, binutils and glibc to the branches
> mentioned above
> 4. cd <patch-to-build-folder>
> 5. <patch-to-riscv-gnu-toolchain>configure
> --prefix=<patch-to-build-folder>build-install --with-arch=rv64gc
> 6. make report-gcc-linux -j32

Instead of me trying to go through this (at least part of which looks like
it won't really fit my normal environment; among other things I would also
prefer to work from upstream gcc, not any RISC-V clone thereof), could you
provide me with the detailed gcc.log and g++.log from the run (I know
they're huge, so you may want to upload them somewhere, or you might simply
extract relevant fragments)? Of course if it would be the complete logs,
then I would also need to know which, if any, FAILs are pre-existing.

From what you write it also doesn't look as if glibc was necessary to
include.

Jan