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/111631] [14 Regression] Wrong code at -Os on x86_64-linux-gnu since r14-3217-g4d6132e5932 Date: Thu, 28 Sep 2023 15:19:07 +0000 [thread overview] Message-ID: <bug-111631-4-0Bb5sqLxeN@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111631-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111631 --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- ldist produces: b_25 = (long int) j_23; d_26 = h; _8 = (sizetype) d_26; _38 = (char *) b_25; __builtin_memset (_38, 0, _8); and also we have: <bb 7> [local count: 13370358]: if (j_23 != 0) goto <bb 10>; [50.00%] else goto <bb 11>; [50.00%] ... <bb 10> [local count: 6685179]: g.10_9 = g; _10 = *g.10_9; _11 = (unsigned short) _10; _12 = _11 + 65535; _13 = (short int) _12; *g.10_9 = _13; But since d_26 is 0, originally there was no deferencing of _38 but now there is and such.
prev parent reply other threads:[~2023-09-28 15:19 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-28 13:57 [Bug tree-optimization/111631] New: " shaohua.li at inf dot ethz.ch 2023-09-28 15:15 ` [Bug tree-optimization/111631] [14 Regression] " pinskia at gcc dot gnu.org 2023-09-28 15:17 ` pinskia at gcc dot gnu.org 2023-09-28 15:19 ` pinskia at gcc dot gnu.org [this message]
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-111631-4-0Bb5sqLxeN@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).