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 c/111760] New: risc-v regression: COND_LEN_* incorrect fold/simplify in middle-end Date: Tue, 10 Oct 2023 14:29:52 +0000 [thread overview] Message-ID: <bug-111760-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111760 Bug ID: 111760 Summary: risc-v regression: COND_LEN_* incorrect fold/simplify in middle-end Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: juzhe.zhong at rivai dot ai Target Milestone: --- FAIL: gcc.dg/vect/vect-cond-arith-2.c -flto -ffat-lto-objects scan-tree-dump optimized " = \\.COND_(LEN_)?SUB" FAIL: gcc.dg/vect/vect-cond-arith-2.c scan-tree-dump optimized " = \\.COND_(LEN_)?SUB" https://godbolt.org/z/hEz51qf6a double __GIMPLE (ssa, startwith("loop")) neg_xi (double *x) { int i; long unsigned int index; long unsigned int offset; double * xi_ptr; double xi; double neg_xi; double res; unsigned int ivtmp; __BB(5): goto __BB2; __BB(2): res_1 = __PHI (__BB5: 0.0, __BB3: res_2); i_4 = __PHI (__BB5: 0, __BB3: i_5); ivtmp_6 = __PHI (__BB5: 100U, __BB3: ivtmp_7); index = (long unsigned int) i_4; offset = index * 8UL; xi_ptr = x_8(D) + offset; xi = *xi_ptr; neg_xi = -xi; res_2 = neg_xi + res_1; i_5 = i_4 + 1; ivtmp_7 = ivtmp_6 - 1U; if (ivtmp_7 != 0U) goto __BB3; else goto __BB4; __BB(3): goto __BB2; __BB(4): res_3 = __PHI (__BB2: res_2); return res_3; } There is no COND_LEN_ADD IR here which is incorrect.
next reply other threads:[~2023-10-10 14:30 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-10 14:29 juzhe.zhong at rivai dot ai [this message] 2023-10-10 17:47 ` [Bug c/111760] " pinskia at gcc dot gnu.org 2023-10-10 21:02 ` [Bug tree-optimization/111760] " rdapp at gcc dot gnu.org 2023-10-10 21:58 ` juzhe.zhong at rivai dot ai 2023-10-10 22:04 ` pinskia at gcc dot gnu.org 2023-10-10 22:08 ` juzhe.zhong at rivai dot ai 2023-10-11 6:47 ` rdapp at gcc dot gnu.org 2023-10-11 8:36 ` rguenth at gcc dot gnu.org 2023-11-06 11:27 ` cvs-commit at gcc dot gnu.org 2023-11-07 23:39 ` juzhe.zhong at rivai dot ai
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-111760-4@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).