Re: [PATCH] RISC-V: Prohibit combination of 'E' and 'H'

[Jeff Law <jeffreyalaw@gmail.com>]

On 10/21/23 19:33, Tsukasa OI wrote:

> 
> Hmm, I generally agree with your opinion and I made a board file for
> DejaGnu (running qemu-riscv64) to run "make check-gcc
> RUNTESTFLAGS='--target_board=riscv-sim riscv.exp'" because it already
> contains many execute tests (and annoys me if I don't do that).
> 
> What I'm not sure is, what kind of regression tests we need?
> 
> (In my mind)
> Level 1: Make nearly empty program with specific -march (and optionally
>           -mabi?) and make sure that it works.
> Level 2: Make a program with inline assembly and execute tests with
>           specific configurations (with specific -march and -mabi)
>           [I'm not sure how to write **and optionally execute tests**]
> 
> I would like to hear your thoughts.
So I don't think we need to do a large matrix of extensions or anything 
like that.  Whatever config you usually build should be sufficient.

What most folks do is a make -k check before/after their patch and 
compare the results.  That's the standard.

If you change a target independent file, then the standard would be to 
bootstrap and regression test on x86 or similar primary architecture.

Jeff