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/113431] [14] RISC-V rv64gcv vector: Runtime mismatch at -O3 Date: Wed, 17 Jan 2024 01:38:44 +0000 [thread overview] Message-ID: <bug-113431-4-LLyIfa9Ce9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113431-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113431 --- Comment #4 from JuzheZhong <juzhe.zhong at rivai dot ai> --- a[0][1] seems to be undefined value. And the test seems to trigger undefined behavior. I just checked ARM SVE and RVV. The vectorized IR is totally the same and I don't see anything obviously wrong in RVV assembler. https://godbolt.org/z/jz866Kfsv Hi, Andrew. Could you confirm it whether ARM SVE has the same behavior as RVV? That is, with vectorized, return 1, whereas no vectorized, return 0;
next prev parent reply other threads:[~2024-01-17 1:38 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-16 21:45 [Bug target/113431] New: " patrick at rivosinc dot com 2024-01-16 21:46 ` [Bug target/113431] " patrick at rivosinc dot com 2024-01-16 22:37 ` juzhe.zhong at rivai dot ai 2024-01-16 22:57 ` patrick at rivosinc dot com 2024-01-17 1:38 ` juzhe.zhong at rivai dot ai [this message] 2024-01-17 1:42 ` patrick at rivosinc dot com 2024-01-17 1:44 ` juzhe.zhong at rivai dot ai 2024-01-17 1:53 ` patrick at rivosinc dot com 2024-01-17 1:56 ` juzhe.zhong at rivai dot ai 2024-01-17 3:33 ` [Bug tree-optimization/113431] [14 Regression] Wrong code " pinskia at gcc dot gnu.org 2024-01-17 8:08 ` rguenth at gcc dot gnu.org 2024-01-17 8:31 ` juzhe.zhong at rivai dot ai 2024-01-17 8:48 ` rguenth at gcc dot gnu.org 2024-01-17 12:34 ` rguenth at gcc dot gnu.org 2024-01-17 12:59 ` rguenth at gcc dot gnu.org 2024-01-18 7:37 ` cvs-commit at gcc dot gnu.org 2024-01-18 7:39 ` rguenth at gcc dot gnu.org 2024-01-19 8:55 ` ro at gcc dot gnu.org 2024-01-19 8:56 ` ro at gcc dot gnu.org 2024-02-28 14:55 ` ro at gcc dot gnu.org 2024-03-15 14:06 ` jakub at gcc dot gnu.org 2024-03-15 15:42 ` rguenth at gcc dot gnu.org 2024-03-15 15:52 ` cvs-commit at gcc dot gnu.org 2024-03-15 15:53 ` jakub at gcc dot gnu.org 2024-03-19 9:44 ` ro at CeBiTec dot Uni-Bielefeld.DE
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-113431-4-LLyIfa9Ce9@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).