public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "krebbel at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/98973] [11 regression] Wrong code with gcse store motion pass Date: Fri, 05 Feb 2021 10:04:36 +0000 [thread overview] Message-ID: <bug-98973-4-C4EjVjN6Bh@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98973-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98973 --- Comment #4 from Andreas Krebbel <krebbel at gcc dot gnu.org> --- The update of global variable c is moved out of the loop. Due to that c stays at 8 although it should be counted down to 2.
next prev parent reply other threads:[~2021-02-05 10:04 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-05 9:10 [Bug rtl-optimization/98973] New: " krebbel at gcc dot gnu.org 2021-02-05 9:15 ` [Bug rtl-optimization/98973] " rguenth at gcc dot gnu.org 2021-02-05 10:02 ` krebbel at gcc dot gnu.org 2021-02-05 10:03 ` krebbel at gcc dot gnu.org 2021-02-05 10:04 ` krebbel at gcc dot gnu.org [this message] 2021-02-05 10:11 ` krebbel at gcc dot gnu.org 2021-02-05 11:54 ` rguenth at gcc dot gnu.org 2021-02-05 12:19 ` jakub at gcc dot gnu.org 2021-02-05 12:39 ` rguenth at gcc dot gnu.org 2021-02-26 12:51 ` rguenth at gcc dot gnu.org 2021-04-09 8:16 ` rguenth at gcc dot gnu.org 2021-04-12 13:16 ` ebotcazou at gcc dot gnu.org 2021-04-13 15:58 ` law at gcc dot gnu.org 2021-04-27 11:40 ` [Bug rtl-optimization/98973] [11/12 " jakub at gcc dot gnu.org 2021-07-28 7:05 ` rguenth at gcc dot gnu.org 2022-04-21 7:48 ` rguenth at gcc dot gnu.org 2023-05-29 10:04 ` [Bug rtl-optimization/98973] [11/12/13/14 " jakub 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-98973-4-C4EjVjN6Bh@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).