> It is true that dwarf debugging information is much bigger in size.
Thanks for confirming. I had read elsewhere that stabs is more inefficient but
clearly that is incorrect.
> But in general you have here different possiblities to solve this.
> First of course by the debugging-level switch -g.
> > Our project (MAME) recently converted a bunch of C code to C++, and
> as a result our symbol size has bloated tremendously (EXE is now
> 280MB(!) with symbols, versus 40MB without), killing our link times.
> Our cohorts on the Linux side have not noticed any significant
> difference. After some
Hi there,
Our project (MAME) recently converted a bunch of C code to C++, and as a result
our symbol size has bloated tremendously (EXE is now 280MB(!) with symbols,
versus 40MB without), killing our link times. Our cohorts on the Linux side
have not noticed any significant difference. After so
> >> Is this built with the Vista fix (-D__USE_MINGW_ACCESS)?
>
> That fix has been included in the build system of GCC itself for
> quite a few months now. You don't need to do anything special to
> benefit from it (apart from using recent mingw headers along).
Apparently so, as I was able to co
> On 3/20/08, Aaron Giles <[EMAIL PROTECTED]> wrote:
> > Is this built with the Vista fix (-D__USE_MINGW_ACCESS)?
>
> Yeah, I'm gonna go with a 'No' on that one But feel free to try
> it :) :)
>
> I suppose I should add Vista to the list of ho
Is this built with the Vista fix (-D__USE_MINGW_ACCESS)?
Aaron
--
> -Original Message-
> From: [EMAIL PROTECTED]
[mailto:mingw-w64-
> [EMAIL PROTECTED] On Behalf Of NightStrike
> Sent: Thursday, March 20, 2008 7:15 AM
> To: whatis neveritis; Kai Tietz
> Cc: mingw-w64-public@lists.sourcefo
