On 11/12/24 11:02 PM, wangf...@eswincomputing.com wrote:
On 2024-11-13 07:30 Edwin Lu <e...@rivosinc.com> wrote:
I took a look at the CI errors today since I remember Jeff checking the
CI output. I don't remember if the errors were the main things blocking
the patch or if there just wasn't any follow up.
Juzhe suggested me to addd some run test case for this patch, but the run case
depends on the qemu flag in the script.
So I will submmit a change for "march-to-cpu-opt" firstly and then update this
patch for the test case.
At the same time, I will merg these case into vector test case, so this issue
would not be haapened.
Thanks.
I'll look into having the CI output some additional test log information
to make understanding failures a lot more user friendly but for now, all
of the (test for excess errors) are "error: 'for' loop initial
declarations are only allowed in C99 or C11 mode".
I didn't have any particular issue in mind -- it was more a "we need to
come to a resolution on the patch" since it'd been sitting in the queue
for a while.
Looking at the CI results, it's failing with:
FAIL: gcc.target/riscv/rvv/autovec/vfncvt-auto-vect.c -O3 -ftree-vectorize
(test for excess errors)
FAIL: gcc.target/riscv/rvv/autovec/vfwcvt-auto-vect.c -O3 -ftree-vectorize
(test for excess errors)
FAIL: gcc.target/riscv/rvv/autovec/vfwmacc-auto-vect.c -O3 -ftree-vectorize
(test for excess errors)
That to me isn't likely to be a QEMU/Spike issue, but is more likely an
unexpected diagnostic from the test, assembler error or the like.
It does sound like you plan to submit a new version, so I'll put the
patch into a subsumed state now.
Jeff
