public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/101066] [10/11/12 Regression] Wrong code after fixup_cfg3 since r10-3311-gff6686d2e5f797d6 Date: Tue, 20 Jul 2021 12:32:40 +0000 [thread overview] Message-ID: <bug-101066-4-3pP781gElC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101066-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101066 Martin Jambor <jamborm at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|ASSIGNED |RESOLVED --- Comment #8 from Martin Jambor <jamborm at gcc dot gnu.org> --- Eventually I decided to backport the full fix to gcc-10 too (as opposed to bailing out more aggresively). So fixed also on all affected branches.
prev parent reply other threads:[~2021-07-20 12:32 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-14 13:45 [Bug c/101066] New: Wrong code after fixup_cfg3 stefansf at linux dot ibm.com 2021-06-15 7:02 ` [Bug tree-optimization/101066] [10/11/12 Regression] Wrong code after fixup_cfg3 since r10-3311-gff6686d2e5f797d6 marxin at gcc dot gnu.org 2021-06-15 7:51 ` rguenth at gcc dot gnu.org 2021-06-15 17:31 ` jamborm at gcc dot gnu.org 2021-06-21 20:18 ` [Bug ipa/101066] " jamborm at gcc dot gnu.org 2021-06-24 11:42 ` stefansf at linux dot ibm.com 2021-07-08 17:46 ` cvs-commit at gcc dot gnu.org 2021-07-09 14:12 ` cvs-commit at gcc dot gnu.org 2021-07-20 12:30 ` cvs-commit at gcc dot gnu.org 2021-07-20 12:32 ` jamborm 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-101066-4-3pP781gElC@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).