public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/97764] [10/11 Regression] wrong code at -O1 and above on x86_64-pc-linux-gnu since r10-6809 Date: Mon, 09 Nov 2020 11:50:47 +0000 [thread overview] Message-ID: <bug-97764-4-lvMbLsi2uH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97764-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97764 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2020-11-09 Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org Ever confirmed|0 |1 Summary|wrong code at -O1 and above |[10/11 Regression] wrong |on x86_64-pc-linux-gnu |code at -O1 and above on | |x86_64-pc-linux-gnu since | |r10-6809 CC| |jakub at gcc dot gnu.org Target Milestone|--- |10.3 --- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Started with my r10-6809-g7f5617b00445dcc861a498a4cecc8aaa59e05b8c
next prev parent reply other threads:[~2020-11-09 11:50 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-09 11:39 [Bug tree-optimization/97764] New: wrong code at -O1 and above on x86_64-pc-linux-gnu zhendong.su at inf dot ethz.ch 2020-11-09 11:50 ` jakub at gcc dot gnu.org [this message] 2020-11-09 12:21 ` [Bug tree-optimization/97764] [10/11 Regression] wrong code at -O1 and above on x86_64-pc-linux-gnu since r10-6809 rguenth at gcc dot gnu.org 2020-11-09 13:53 ` jakub at gcc dot gnu.org 2020-11-10 10:18 ` cvs-commit at gcc dot gnu.org 2020-11-10 10:21 ` cvs-commit at gcc dot gnu.org 2020-11-10 10:33 ` rguenth at gcc dot gnu.org 2020-11-10 10:35 ` jakub at gcc dot gnu.org 2020-12-01 11:29 ` 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-97764-4-lvMbLsi2uH@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).