J Decker
2017-03-12 22:39:55 UTC
I have like
H:\build\mingw64-x86-d\sack\debug_out\core\bin>gcc -v
Using built-in specs.
COLLECT_GCC=C:\tools\mingw-w64\i686-5.3.0-win32-sjlj-rt_
v4-rev0\mingw32\bin\gcc.EXE
COLLECT_LTO_WRAPPER=C:/tools/mingw-w64/i686-5.3.0-win32-
sjlj-rt_v4-rev0/mingw32/bin/../libexec/gcc/i686-w64-mingw32/
5.3.0/lto-wrapper.exe
Target: i686-w64-mingw32
and the debug output is 17M . I could understand 2-3M; it's usually 800K
for release mode...
but for like ALL library outputs there's a huge bloat; is this a bug?
Feature? Should I use a different version?
is it SJLJ version that if I get the 6.3 it'll still do that? I should get
dwarf?
H:\build\mingw64-x86-d\sack\debug_out\core\bin>gcc -v
Using built-in specs.
COLLECT_GCC=C:\tools\mingw-w64\i686-5.3.0-win32-sjlj-rt_
v4-rev0\mingw32\bin\gcc.EXE
COLLECT_LTO_WRAPPER=C:/tools/mingw-w64/i686-5.3.0-win32-
sjlj-rt_v4-rev0/mingw32/bin/../libexec/gcc/i686-w64-mingw32/
5.3.0/lto-wrapper.exe
Target: i686-w64-mingw32
and the debug output is 17M . I could understand 2-3M; it's usually 800K
for release mode...
but for like ALL library outputs there's a huge bloat; is this a bug?
Feature? Should I use a different version?
is it SJLJ version that if I get the 6.3 it'll still do that? I should get
dwarf?