public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/110582] [14 Regression] Wrong code at -O2/3 on x86_64-linux-gnu Date: Fri, 07 Jul 2023 11:19:52 +0000 [thread overview] Message-ID: <bug-110582-4-sZvS8Mt6AA@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110582-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110582 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P3 |P1 CC| |amacleod at redhat dot com --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- It works with -fno-tree-loop-optimize but the difference from loop opts is just int main () { int D.2782; int b_lsm.13; int a_lsm.12; char c; - unsigned char c.6_2; - unsigned char _3; int iftmp.1_11; int _12(D); int iftmp.1_15; + unsigned char ivtmp_36; + unsigned char ivtmp_37; int _38; long int _39; long int _40; @@ -23,8 +21,8 @@ <bb 2> [local count: 10737416]: <bb 3> [local count: 1063004409]: - # c_21 = PHI <c_18(5), 0(2)> # a_lsm.12_4 = PHI <iftmp.1_11(5), 0(2)> + # ivtmp_37 = PHI <ivtmp_36(5), 253(2)> if (a_lsm.12_4 != 0) goto <bb 4>; [50.00%] else @@ -35,10 +33,8 @@ <bb 5> [local count: 1063004409]: # iftmp.1_11 = PHI <iftmp.1_15(4), 2(3)> - c.6_2 = (unsigned char) c_21; - _3 = c.6_2 + 1; - c_18 = (char) _3; - if (c_18 != -3) + ivtmp_36 = ivtmp_37 - 1; + if (ivtmp_36 != 0) goto <bb 3>; [98.99%] else with that indeed threadfull2 miscompiles this somehow. Andrew?
next prev parent reply other threads:[~2023-07-07 11:19 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-07 8:03 [Bug c/110582] New: " shaohua.li at inf dot ethz.ch 2023-07-07 8:40 ` [Bug tree-optimization/110582] [14 Regression] " pinskia at gcc dot gnu.org 2023-07-07 11:19 ` rguenth at gcc dot gnu.org [this message] 2023-07-08 1:08 ` pinskia at gcc dot gnu.org 2023-07-08 1:17 ` pinskia at gcc dot gnu.org 2023-07-30 14:46 ` shaohua.li at inf dot ethz.ch 2023-07-31 16:06 ` cvs-commit at gcc dot gnu.org 2023-07-31 16:11 ` amacleod at redhat 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-110582-4-sZvS8Mt6AA@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).