From: Patrick O'Neill <patrick@rivosinc.com>
To: Palmer Dabbelt <palmer@rivosinc.com>
Cc: juzhe.zhong@rivai.ai, rdapp.gcc@gmail.com,
gcc-patches@gcc.gnu.org, kito.cheng@sifive.com,
jeffreyalaw@gmail.com, ewlu@rivosinc.com,
joern.rennecke@embecosm.com, jeremy.bennett@embecosm.com,
gnu-toolchain@rivosinc.com
Subject: Re: [Committed] RISC-V: Support VLS unary floating-point patterns
Date: Thu, 21 Sep 2023 09:14:35 -0700 [thread overview]
Message-ID: <54c4db48-fb70-02a8-d766-b4acdb3fcb4b@rivosinc.com> (raw)
In-Reply-To: <mhng-4d6a00f2-0591-4d21-8def-ce8e78bcd555@palmer-ri-x1c9a>
On 9/21/23 03:20, Palmer Dabbelt wrote:
> On Wed, 20 Sep 2023 10:47:23 PDT (-0700), Patrick O'Neill wrote:
>> ...
>>
>> [1]:
>> Executing on host:
>> /github/ewlu-runner-2/_work/riscv-gnu-toolchain/riscv-gnu-toolchain/build/build-gcc-linux-stage2/gcc/xgcc
>>
>> -B/github/ewlu-runner-2/_work/riscv-gnu-toolchain/riscv-gnu-toolchain/build/build-gcc-linux-stage2/gcc/
>>
>> /github/ewlu-runner-2/_work/riscv-gnu-toolchain/riscv-gnu-toolchain/gcc/gcc/testsuite/gcc.target/riscv/rvv/autovec/math-ceil-1.c
>>
>> -march=rv32gcv -mabi=ilp32d -mcmodel=medlow -fdiagnostics-plain-output
>> -O3 -ftree-vectorize -march=rv64gcv -mabi=lp64d -O3 -ftree-vectorize
>> -fno-vect-cost-model -ffast-math -fno-schedule-insns
>> -fno-schedule-insns2 -S -o math-ceil-1.s (timeout = 600)
>> spawn -ignore SIGHUP
>> /github/ewlu-runner-2/_work/riscv-gnu-toolchain/riscv-gnu-toolchain/build/build-gcc-linux-stage2/gcc/xgcc
>>
>> -B/github/ewlu-runner-2/_work/riscv-gnu-toolchain/riscv-gnu-toolchain/build/build-gcc-linux-stage2/gcc/
>>
>> /github/ewlu-runner-2/_work/riscv-gnu-toolchain/riscv-gnu-toolchain/gcc/gcc/testsuite/gcc.target/riscv/rvv/autovec/math-ceil-1.c
>>
>> -march=rv32gcv -mabi=ilp32d -mcmodel=medlow -fdiagnostics-plain-output
>> -O3 -ftree-vectorize -march=rv64gcv -mabi=lp64d -O3 -ftree-vectorize
>> -fno-vect-cost-model -ffast-math -fno-schedule-insns
>> -fno-schedule-insns2 -S -o math-ceil-1.s
>> In file included from
>> /github/ewlu-runner-2/_work/riscv-gnu-toolchain/riscv-gnu-toolchain/build/sysroot/usr/include/features.h:515,
>>
>> from
>> /github/ewlu-runner-2/_work/riscv-gnu-toolchain/riscv-gnu-toolchain/build/sysroot/usr/include/bits/libc-header-start.h:33,
>>
>> from
>> /github/ewlu-runner-2/_work/riscv-gnu-toolchain/riscv-gnu-toolchain/build/sysroot/usr/include/math.h:27,
>>
>> from
>> /github/ewlu-runner-2/_work/riscv-gnu-toolchain/riscv-gnu-toolchain/gcc/gcc/testsuite/gcc.target/riscv/rvv/autovec/test-math.h:1,
>>
>> from
>> /github/ewlu-runner-2/_work/riscv-gnu-toolchain/riscv-gnu-toolchain/gcc/gcc/testsuite/gcc.target/riscv/rvv/autovec/math-ceil-1.c:5:
>>
>> /github/ewlu-runner-2/_work/riscv-gnu-toolchain/riscv-gnu-toolchain/build/sysroot/usr/include/gnu/stubs.h:17:11:
>>
>> fatal error: gnu/stubs-lp64d.h: No such file or directory
>
> That looks like a toolchain build/configuration issue, not a test
> issue. IIRC this comes up from time to time, something's probably
> broken in riscv-gnu-toolchain but I'm not sure what's wrong.
>
> I get a working setup with just `./configure --enable-linux
> --disable-multilib` and the latest riscv-gnu-toolchain master. How are
> you building things?
I've kicked off a few builds to confirm but I use:
git clone https://github.com/riscv-collab/riscv-gnu-toolchain
cd riscv-gnu-toolchain
git submodule update --init gcc
cd gcc && git checkout master && cd ..
mkdir build && cd build
../configure --prefix=$(pwd) --with-arch=rv32gcv --with-abi=ilp32d
Make sure you bump gcc to tip of tree!
The latest riscv-gnu-toolchain master uses gcc 12.2 which doesn't have
the testcases that are failing (rvv folder):
https://github.com/gcc-mirror/gcc/tree/2ee5e4300186a92ad73f1a1a64cb918dc76c8d67/gcc/testsuite/gcc.target/riscv
The failures only show up for tests in:
gcc.target/riscv/rvv/
gcc.dg/vect/costmodel/riscv/rvv/
After bumping gcc and using your command (with --prefix)
../configure --enable-linux --disable-multilib --prefix=$(pwd)
I still get the missing stubs failures.
I've also tried this with the build directory both inside and outside
the repo and that doesn't make a difference.
Patrick
>
>> compilation terminated.
>> compiler exited with status 1
>> FAIL: gcc.target/riscv/rvv/autovec/math-ceil-1.c -O3 -ftree-vectorize
>> (test for excess errors)
>>
>> [2]:
>> https://github.com/ewlu/riscv-gnu-toolchain/issues/170
>>
>> [3]:
>> This also extends beyond math.h. I'm seeing similar failures for
>> testcases like
>> gcc.target/riscv/rvv/autovec/cond/cond_convert_int2float-rv64-1.c that
>> #include <stdint.h>.
next prev parent reply other threads:[~2023-09-21 16:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 11:26 Juzhe-Zhong
2023-09-20 0:34 ` Patrick O'Neill
2023-09-20 0:43 ` juzhe.zhong
2023-09-20 0:52 ` Kito Cheng
2023-09-20 0:54 ` juzhe.zhong
2023-09-20 1:12 ` Patrick O'Neill
2023-09-20 17:47 ` Patrick O'Neill
2023-09-20 22:00 ` 钟居哲
2023-09-21 10:20 ` Palmer Dabbelt
2023-09-21 11:24 ` Kito Cheng
2023-09-21 11:26 ` Palmer Dabbelt
2023-09-21 16:14 ` Patrick O'Neill [this message]
2023-09-21 17:43 ` Patrick O'Neill
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54c4db48-fb70-02a8-d766-b4acdb3fcb4b@rivosinc.com \
--to=patrick@rivosinc.com \
--cc=ewlu@rivosinc.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gnu-toolchain@rivosinc.com \
--cc=jeffreyalaw@gmail.com \
--cc=jeremy.bennett@embecosm.com \
--cc=joern.rennecke@embecosm.com \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@sifive.com \
--cc=palmer@rivosinc.com \
--cc=rdapp.gcc@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).