public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/104180] [10/11/12 Regression] '-fcompare-debug' failure (length) w/ -O1
Date: Mon, 24 Jan 2022 09:10:10 +0000 [thread overview]
Message-ID: <bug-104180-4-L7ULGk0A7A@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104180-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104180
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P2
CC| |rguenth at gcc dot gnu.org
--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
I think it's reasonable to turn them off (OTOH we then probably lose all test
coverage). IIRC gdb doensn't handle any of the advanced debug stuff GCC emits
(like views)?
next prev parent reply other threads:[~2022-01-24 9:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-22 8:31 [Bug debug/104180] New: " asolokha at gmx dot com
2022-01-22 11:13 ` [Bug debug/104180] " jakub at gcc dot gnu.org
2022-01-22 12:06 ` [Bug c++/104180] " pinskia at gcc dot gnu.org
2022-01-22 12:07 ` pinskia at gcc dot gnu.org
2022-01-22 12:19 ` jakub at gcc dot gnu.org
2022-01-24 9:10 ` rguenth at gcc dot gnu.org [this message]
2022-01-24 9:30 ` asolokha at gmx dot com
2022-02-17 6:23 ` aoliva at gcc dot gnu.org
2022-06-28 10:47 ` [Bug c++/104180] [10/11/12/13 " jakub at gcc dot gnu.org
2023-07-07 10:42 ` [Bug c++/104180] [11/12/13/14 " 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-104180-4-L7ULGk0A7A@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: link
Be 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).