summaryrefslogtreecommitdiff
path: root/set_soenv.in
diff options
context:
space:
mode:
authorLuboš Luňák <l.lunak@suse.cz>2011-12-15 16:59:17 +0100
committerLuboš Luňák <l.lunak@suse.cz>2011-12-15 17:02:36 +0100
commite87fc0bfde8bd48b449e123c1bdd28e1359e8c77 (patch)
tree63947d2f20cd72567fd85646e5fa386ba4e2e7bc /set_soenv.in
parentf269629d1b0182d89b2f5a769fbb0f8dcb815ec3 (diff)
Revert "enable -gdwarf-4 by default if possible"
It turns out even quite recent gdb (7.1) reportedly does not support DWARF4, moreover while the produced binaries are smaller, faster and make gdb initially use less memory, this quickly ceases to the case as soon as one actually does anything in gdb. Presumably the DWARF4 handling in current gdb is very inefficient (http://sourceware.org/bugzilla/show_bug.cgi?id=13498). This reverts commit 5214f7843ca48f2207945fbfe32ba164afe7b3aa. Conflicts: solenv/gbuild/platform/WNT_INTEL_GCC.mk solenv/gbuild/platform/unxgcc.mk
Diffstat (limited to 'set_soenv.in')
-rwxr-xr-xset_soenv.in1
1 files changed, 0 insertions, 1 deletions
diff --git a/set_soenv.in b/set_soenv.in
index 2150be5a6551..150636662ea7 100755
--- a/set_soenv.in
+++ b/set_soenv.in
@@ -1700,7 +1700,6 @@ ToFile( "HAVE_GCC_VISIBILITY_FEATURE",
"@HAVE_GCC_VISIBILITY_FEATURE@", "e" );
ToFile( "HAVE_GCC_VISIBILITY_BROKEN",
"@HAVE_GCC_VISIBILITY_BROKEN@", "e" );
-ToFile( "HAVE_GCC_DWARF_4","@HAVE_GCC_DWARF_4@","e" );
ToFile( "HAVE_LD_HASH_STYLE","@HAVE_LD_HASH_STYLE@","e" );
ToFile( "WITH_LINKER_HASH_STYLE","@WITH_LINKER_HASH_STYLE@","e" );
ToFile( "HAVE_LD_BSYMBOLIC_FUNCTIONS",