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 debug/104050] '-fcompare-debug' failure w/ -std=c++20 -O1 Date: Mon, 17 Jan 2022 10:41:53 +0000 [thread overview] Message-ID: <bug-104050-4-beAT92qnEG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104050-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104050 Martin Liška <marxin at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[12 Regression] |'-fcompare-debug' failure |[coroutines] |w/ -std=c++20 -O1 |'-fcompare-debug' failure | |w/ -std=c++20 -O1 | Ever confirmed|0 |1 CC| |iains at gcc dot gnu.org, | |marxin at gcc dot gnu.org Last reconfirmed| |2022-01-17 Status|UNCONFIRMED |NEW --- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> --- Confirmed. Interesting that one needs -save-temps. Likely started with GCC 11.
next prev parent reply other threads:[~2022-01-17 10:41 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-16 14:36 [Bug debug/104050] New: [12 Regression] [coroutines] " asolokha at gmx dot com 2022-01-17 8:36 ` [Bug debug/104050] " rguenth at gcc dot gnu.org 2022-01-17 10:41 ` marxin at gcc dot gnu.org [this message] 2022-04-18 14:50 ` [Bug debug/104050] " iains at gcc dot gnu.org 2022-05-06 8:32 ` jakub at gcc dot gnu.org 2023-05-08 12:23 ` rguenth 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-104050-4-beAT92qnEG@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).