public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/114476] [13/14 Regression] wrong code with -fwrapv -O3 -fno-vector-cost-mode (and -march=armv9-a+sve2 on aarch64 and -march=rv64gcv on riscv) Date: Tue, 26 Mar 2024 05:10:32 +0000 [thread overview] Message-ID: <bug-114476-4-vpSCkfVV4o@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114476-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114476 --- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Here is a testcase where we don't need -fwrapv: ``` signed int b = 9; int c[23][23]; signed int d[23]; int main() { for (int h = 0; h < 23; h += 2) { c[h][h] = d[h]; b= -b; } __builtin_printf("%u\n", b); } ```
next prev parent reply other threads:[~2024-03-26 5:10 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-26 4:34 [Bug target/114476] New: [14] RISC-V rv64gcv vector: Runtime mismatch at -O3 patrick at rivosinc dot com 2024-03-26 5:04 ` [Bug tree-optimization/114476] [13/14 Regression] wrong code with -fwrapv -O3 -fno-vector-cost-mode (and -march=armv9-a+sve2 on aarch64 and -march=rv64gcv on riscv) pinskia at gcc dot gnu.org 2024-03-26 5:05 ` pinskia at gcc dot gnu.org 2024-03-26 5:10 ` pinskia at gcc dot gnu.org [this message] 2024-03-26 5:16 ` pinskia at gcc dot gnu.org 2024-03-26 8:07 ` rguenth at gcc dot gnu.org 2024-03-26 12:47 ` rdapp at gcc dot gnu.org 2024-03-27 21:03 ` [Bug tree-optimization/114476] [13/14 Regression] wrong code with -fwrapv -O3 -fno-vect-cost-model " pinskia at gcc dot gnu.org 2024-04-03 1:48 ` juzhe.zhong at rivai dot ai 2024-04-03 12:05 ` rdapp at gcc dot gnu.org
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-114476-4-vpSCkfVV4o@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).