public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/97989] -g3 somehow breaks -E Date: Tue, 01 Dec 2020 08:40:21 +0000 [thread overview] Message-ID: <bug-97989-4-it8rHShFob@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97989-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97989 --- Comment #24 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:934a54180541d27139aecbd19e7f50cb73552c7c commit r11-5596-g934a54180541d27139aecbd19e7f50cb73552c7c Author: Jakub Jelinek <jakub@redhat.com> Date: Tue Dec 1 09:39:04 2020 +0100 driver: Don't imply -dD for -g3 -g0 [PR97989] The driver enables -dD when preprocessing when -g3 is specified, for obvious reasons that we need the macros to be preserved somewhere for them to make up the debug info. But it enables it even if -g3 is later overridden to -g2, -g1 or -g0, where we in the end don't emit .debug_mac{ros,info}. The following patch passes -dD only if we'll need it. 2020-12-01 Jakub Jelinek <jakub@redhat.com> PR debug/97989 * gcc.c (cpp_unique_options): Add -dD if %:debug-level-gt(2) rather than g3|ggdb3|gstabs3|gxcoff3|gvms3. * gcc.dg/cpp/pr97989-1.c: New test. * gcc.dg/cpp/pr97989-2.c: New test.
next prev parent reply other threads:[~2020-12-01 8:40 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-25 16:21 [Bug debug/97989] New: " stsp at users dot sourceforge.net 2020-11-25 16:27 ` [Bug debug/97989] " jakub at gcc dot gnu.org 2020-11-25 17:02 ` pinskia at gcc dot gnu.org 2020-11-25 17:07 ` jakub at gcc dot gnu.org 2020-11-25 17:10 ` stsp at users dot sourceforge.net 2020-11-25 17:13 ` jakub at gcc dot gnu.org 2020-11-25 17:21 ` stsp at users dot sourceforge.net 2020-11-25 17:39 ` jakub at gcc dot gnu.org 2020-11-25 17:44 ` stsp at users dot sourceforge.net 2020-11-25 17:46 ` jakub at gcc dot gnu.org 2020-11-25 17:50 ` stsp at users dot sourceforge.net 2020-11-25 17:51 ` jakub at gcc dot gnu.org 2020-11-25 18:05 ` stsp at users dot sourceforge.net 2020-11-25 18:14 ` jakub at gcc dot gnu.org 2020-11-25 18:22 ` stsp at users dot sourceforge.net 2020-11-25 18:28 ` jakub at gcc dot gnu.org 2020-11-26 12:02 ` stsp at users dot sourceforge.net 2020-11-26 12:09 ` jakub at gcc dot gnu.org 2020-11-26 12:34 ` stsp at users dot sourceforge.net 2020-11-26 12:53 ` jakub at gcc dot gnu.org 2020-11-26 13:40 ` stsp at users dot sourceforge.net 2020-11-26 14:10 ` stsp at users dot sourceforge.net 2020-11-26 14:16 ` jakub at gcc dot gnu.org 2020-11-26 14:30 ` stsp at users dot sourceforge.net 2020-12-01 8:40 ` cvs-commit at gcc dot gnu.org [this message] 2020-12-01 9:15 ` 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-97989-4-it8rHShFob@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).