2013/3/27 Jon :
> 4) For 64-bit C++ code, the current "best" recommendation is dwarf+seh when
> using 4.8.0+ unless one has other constraints.
AFAIU seh+posix or seh+win32. dwarf+seh makes no sense. dwarf is
just available for debugging on x64 and has nothing to do with
exception handling.
> A
> > I'm using the rubenvb with no "dw2" in the archive name, so I suppose I'm
> > using SJLJ in 32bit and SEH in 64bit?
>
> I guess so.
>
> > Can there be a 30% speed difference just due to SJLJ, even if I do not use
> > any
> > exception handling in my code?
>
> Yes, actually I had measured a
2013/3/27 Koehne Kai
> > -Original Message-
> > From: Etienne Sandré-Chardonnal [mailto:etienne.san...@m4x.org]
> > Sent: Wednesday, March 27, 2013 3:43 PM
> > To: mingw-w64-public@lists.sourceforge.net
> > Subject: Re: [Mingw-w64-public] Performance chang
> -Original Message-
> From: Etienne Sandré-Chardonnal [mailto:etienne.san...@m4x.org]
> Sent: Wednesday, March 27, 2013 3:43 PM
> To: mingw-w64-public@lists.sourceforge.net
> Subject: Re: [Mingw-w64-public] Performance changes when switching to
> 4.8.0
>
> I
I'm using the rubenvb with no "dw2" in the archive name, so I suppose
I'm using SJLJ in 32bit and SEH in 64bit?
Can there be a 30% speed difference just due to SJLJ, even if I do not
use any exception handling in my code? Other libs may use exceptions,
but my app is running my code 99% of the time
> -Original Message-
> From: Etienne Sandré-Chardonnal [mailto:etienne.san...@m4x.org]
> Sent: Wednesday, March 27, 2013 3:12 PM
> To: mingw-w64-public@lists.sourceforge.net
> Subject: [Mingw-w64-public] Performance changes when switching to 4.8.0
>
> Dear all,
>
Dear all,
Until a few days ago, I was using:
- Old mingw32 shipped with Qt (gcc 4.4.0) for 32bit builds
- Mingw-w64 x86_64 rubenvb build (gcc 4.7.1)
My code (an intensive calculation) was running at similar speed with
32-bit and 64-bit build (speed index : 510-520, only a few %
difference betwe
