public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>
To: "Andreas Schwab" <schwab@suse.de>,
	 gcc-patches <gcc-patches@gcc.gnu.org>
Cc: kito.cheng <kito.cheng@gmail.com>,
	 collison <collison@rivosinc.com>,  palmer <palmer@dabbelt.com>,
	 jeffreyalaw <jeffreyalaw@gmail.com>,
	 "Robin Dapp" <rdapp.gcc@gmail.com>
Subject: Re: Re: [PATCH] riscv: Add autovectorization tests for binary integer
Date: Mon, 15 May 2023 17:15:41 +0800	[thread overview]
Message-ID: <7D68FA8D7836B5C4+2023051517154059195066@rivai.ai> (raw)
In-Reply-To: <mvmo7mmj6y5.fsf@suse.de>

[-- Attachment #1: Type: text/plain, Size: 1454 bytes --]

I think it is the issue of include file.

Kito may know the better the solution instead of changing stdint.h into stdint-gcc.h.

Thanks.


juzhe.zhong@rivai.ai
 
From: Andreas Schwab
Date: 2023-05-15 17:10
To: Robin Dapp via Gcc-patches
CC: juzhe.zhong@rivai.ai; Kito Cheng; Michael Collison; palmer; jeffreyalaw; Robin Dapp
Subject: Re: [PATCH] riscv: Add autovectorization tests for binary integer
In file included from /usr/include/features.h:515,
                 from /usr/include/bits/libc-header-start.h:33,
                 from /usr/include/stdint.h:26,
                 from /daten/riscv64/gcc/gcc-20230512/Build/gcc/include/stdint.h:9,
                 from /daten/riscv64/gcc/gcc-20230512/gcc/testsuite/gcc.target/riscv/rvv/autovec/binop/shift-template.h:1,
                 from /daten/riscv64/gcc/gcc-20230512/gcc/testsuite/gcc.target/riscv/rvv/autovec/binop/shift-rv32gcv.c:4:
/usr/include/gnu/stubs.h:11:11: fatal error: gnu/stubs-ilp32d.h: No such file or directory
compilation terminated.
compiler exited with status 1
FAIL: gcc.target/riscv/rvv/autovec/binop/shift-rv32gcv.c (test for excess errors)
Excess errors:
/usr/include/gnu/stubs.h:11:11: fatal error: gnu/stubs-ilp32d.h: No such file or directory
compilation terminated.
 
 
-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
 

  reply	other threads:[~2023-05-15  9:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-10 15:24 Robin Dapp
2023-05-10 19:19 ` Palmer Dabbelt
2023-05-11  2:26   ` Kito Cheng
2023-05-11  3:30     ` Jeff Law
2023-05-11 10:27     ` [PATCH v2] RISC-V: Add autovectorization tests for binary integer, operations Robin Dapp
2023-05-11 10:35       ` juzhe.zhong
2023-05-11 11:09         ` Kito Cheng
2023-05-11  2:32 ` [PATCH] riscv: Add autovectorization tests for binary integer juzhe.zhong
2023-05-15  9:10 ` Andreas Schwab
2023-05-15  9:15   ` juzhe.zhong [this message]
2023-05-16  4:19     ` Jeff Law

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=7D68FA8D7836B5C4+2023051517154059195066@rivai.ai \
    --to=juzhe.zhong@rivai.ai \
    --cc=collison@rivosinc.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jeffreyalaw@gmail.com \
    --cc=kito.cheng@gmail.com \
    --cc=palmer@dabbelt.com \
    --cc=rdapp.gcc@gmail.com \
    --cc=schwab@suse.de \
    /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).