public inbox for libstdc++-cvs@sourceware.org help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org Subject: [gcc r12-6751] libstdc++: Remove -gdwarf-4 from flags for debug library Date: Wed, 19 Jan 2022 20:40:01 +0000 (GMT) [thread overview] Message-ID: <20220119204001.5E43C385841B@sourceware.org> (raw) https://gcc.gnu.org/g:fe3e978027724f28d3e15747c991844793d42922 commit r12-6751-gfe3e978027724f28d3e15747c991844793d42922 Author: Jonathan Wakely <jwakely@redhat.com> Date: Wed Jan 19 19:29:42 2022 +0000 libstdc++: Remove -gdwarf-4 from flags for debug library The default is -gdwarf-5 now, so this is hurting rather than improving things. libstdc++-v3/ChangeLog: * configure.ac (GLIBCXX_ENABLE_DEBUG_FLAGS): Remove -gdwarf-4 from default flags. * configure: Regenerate. Diff: --- libstdc++-v3/configure | 4 ++-- libstdc++-v3/configure.ac | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/libstdc++-v3/configure b/libstdc++-v3/configure index 6b7cd24c7cd..4c20c669144 100755 --- a/libstdc++-v3/configure +++ b/libstdc++-v3/configure @@ -1635,7 +1635,7 @@ Optional Features: --enable-concept-checks use Boost-derived template checks [default=no] --enable-libstdcxx-debug-flags=FLAGS pass compiler FLAGS when building debug library - [default="-gdwarf-4 -g3 -O0 -D_GLIBCXX_ASSERTIONS"] + [default="-g3 -O0 -D_GLIBCXX_ASSERTIONS"] --enable-libstdcxx-debug build extra debug library [default=no] --enable-cxx-flags=FLAGS @@ -18578,7 +18578,7 @@ if test "${enable_libstdcxx_debug_flags+set}" = set; then : *) as_fn_error $? "--enable-libstdcxx-debug-flags needs compiler flags as arguments" "$LINENO" 5 ;; esac else - enable_libstdcxx_debug_flags="-gdwarf-4 -g3 -O0 -D_GLIBCXX_ASSERTIONS" + enable_libstdcxx_debug_flags="-g3 -O0 -D_GLIBCXX_ASSERTIONS" fi diff --git a/libstdc++-v3/configure.ac b/libstdc++-v3/configure.ac index 2a3bc520501..e59bcdb2944 100644 --- a/libstdc++-v3/configure.ac +++ b/libstdc++-v3/configure.ac @@ -172,7 +172,7 @@ GLIBCXX_ENABLE_LONG_LONG([yes]) GLIBCXX_ENABLE_WCHAR_T([yes]) GLIBCXX_ENABLE_C99([yes]) GLIBCXX_ENABLE_CONCEPT_CHECKS([no]) -GLIBCXX_ENABLE_DEBUG_FLAGS(["-gdwarf-4 -g3 -O0 -D_GLIBCXX_ASSERTIONS"]) +GLIBCXX_ENABLE_DEBUG_FLAGS(["-g3 -O0 -D_GLIBCXX_ASSERTIONS"]) GLIBCXX_ENABLE_DEBUG([no]) GLIBCXX_ENABLE_PARALLEL([yes]) GLIBCXX_ENABLE_CXX_FLAGS
reply other threads:[~2022-01-19 20:40 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220119204001.5E43C385841B@sourceware.org \ --to=redi@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ --cc=libstdc++-cvs@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).