public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "juzhe.zhong at rivai dot ai" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/112801] [14] RISC-V vector: failure to mask top bits during type conversion Date: Fri, 01 Dec 2023 02:49:38 +0000 [thread overview] Message-ID: <bug-112801-4-OLVMJQGnKs@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112801-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112801 --- Comment #1 from JuzheZhong <juzhe.zhong at rivai dot ai> --- Known issue for a long time. I realized that 2 years ago: https://github.com/riscv-collab/riscv-gnu-toolchain/issues/1075 when I developed the first version of RVV GCC (rvv-next). I don't think it is serious issue since I chose to ignore this issue and correctly work fine in all my downstream application. This issue is also exposed in our regression: FAIL: gcc.dg/signbit-5.c execution test I ignore this FAIL for a long time. Low priority for me and I won't work on fixing it.
next prev parent reply other threads:[~2023-12-01 2:49 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-01 2:41 [Bug target/112801] New: " patrick at rivosinc dot com 2023-12-01 2:49 ` juzhe.zhong at rivai dot ai [this message] 2023-12-01 7:57 ` [Bug target/112801] " rguenth at gcc dot gnu.org 2023-12-01 8:26 ` juzhe.zhong at rivai dot ai 2023-12-02 3:38 ` cvs-commit at gcc dot gnu.org 2023-12-02 3:38 ` juzhe.zhong at rivai dot ai 2023-12-04 17:25 ` patrick at rivosinc dot com
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=bug-112801-4-OLVMJQGnKs@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /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: linkBe 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).