This is the mail archive of the
mailing list for the GCC project.
g++ 4.2, cygwin, NUMA awareness issue
- From: tbp <tbptbp at gmail dot com>
- To: gcc at gcc dot gnu dot org
- Date: Tue, 1 Aug 2006 03:52:05 +0200
- Subject: g++ 4.2, cygwin, NUMA awareness issue
As i don't know which party (g++, stdc++, cygwin) to put the blame on
i'll start here.
I've traced back a weird performance issue to a 'new' returning non
cpu-local memory but only when the binary is launched from the
shell/console. That suggests some crt friction.
(threads where those allocations happen are properly binded to one cpu)
That's on xp sp2, on a bi-k8 box with
Using built-in specs.
Configured with: ../configure --prefix=/usr/local/gcc-4.2-20060624
-threads=posix --with-system-zlib --disable-checking --disable-nls
registry --verbose --enable-bootstrap --with-gcc --with-gnu-ld
Thread model: posix
gcc version 4.2.0 20060624 (experimental)
Does that ring a bell or shall i move along the chain? :)