public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/104156] [12 Regression] -fcompare-debug failure with -O2 -funswitch-loops since r12-4526-gd8edfadfc7a9795b Date: Fri, 21 Jan 2022 08:27:31 +0000 [thread overview] Message-ID: <bug-104156-4-olZtKVwEdR@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104156-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104156 Martin Liška <marxin at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marxin at gcc dot gnu.org, | |rguenth at gcc dot gnu.org Keywords|needs-bisection | Summary|[12 Regression] |[12 Regression] |-fcompare-debug failure |-fcompare-debug failure |with -O2 -funswitch-loops |with -O2 -funswitch-loops | |since | |r12-4526-gd8edfadfc7a9795b --- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> --- Started with r12-4526-gd8edfadfc7a9795b.
next prev parent reply other threads:[~2022-01-21 8:27 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-21 4:57 [Bug c/104156] New: -fcompare-debug failure with -O3 cnsun at uwaterloo dot ca 2022-01-21 8:17 ` [Bug tree-optimization/104156] [12 Regression] " pinskia at gcc dot gnu.org 2022-01-21 8:27 ` marxin at gcc dot gnu.org [this message] 2022-01-21 8:42 ` [Bug tree-optimization/104156] [12 Regression] -fcompare-debug failure with -O2 -funswitch-loops since r12-4526-gd8edfadfc7a9795b pinskia at gcc dot gnu.org 2022-01-21 9:00 ` rguenth at gcc dot gnu.org 2022-01-21 11:19 ` cvs-commit at gcc dot gnu.org 2022-01-21 11:22 ` rguenth at gcc dot gnu.org 2022-01-22 2:22 ` cnsun at uwaterloo dot ca 2022-01-22 20:15 ` pinskia at gcc dot gnu.org 2022-01-22 21:37 ` cnsun at uwaterloo dot ca 2022-01-24 7:57 ` rguenther at suse dot de
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-104156-4-olZtKVwEdR@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).