By: GiGNiC (e.delete@this.ma.il), December 8, 2014 11:53 am
Room: Moderated Discussions
Eric Bron (eric.bron.delete@this.zvisuel.privatefortest.com) on December 8, 2014 4:17 am wrote:
> > Thanks for collecting the perf results.
>
> just to make it clear, these are the perf results in the GiGNiC post (with undisclosed
> compiler version and test platform), not something I have tested personnaly
It was Visual Studio 2013 Update 4 (VC12), default project settings*, code built in 32bit Release mode. (64bit gave the same results)
The test was run on a Core i5-3470 (4-core Ivy Bridge, no HT), Windows 7 64bit.
* VS reports the following equivalent command line:
> > Thanks for collecting the perf results.
>
> just to make it clear, these are the perf results in the GiGNiC post (with undisclosed
> compiler version and test platform), not something I have tested personnaly
It was Visual Studio 2013 Update 4 (VC12), default project settings*, code built in 32bit Release mode. (64bit gave the same results)
The test was run on a Core i5-3470 (4-core Ivy Bridge, no HT), Windows 7 64bit.
* VS reports the following equivalent command line:
/GS /GL /analyze- /W3 /Gy /Zc:wchar_t /Zi /Gm- /O2 /sdl /Fd"Releasevc120.pdb" /fp:precise /D "_MBCS" /errorReport:prompt /WX- /Zc:forScope /Gd /Oy- /Oi /MD /Fa"Release" /EHsc /nologo /Fo"Release" /Fp"ReleaseMutexPerformance.pch"
