Ian Lance Taylor [EMAIL PROTECTED] writes:
Chad Attermann [EMAIL PROTECTED] writes:
I can not confirm that it was the i386 code included in the gcc build
but it appears that way from the signature. Is this perhaps a problem
with the way that gcc 3.4.3 shipping with Solaris 10 x86 was
Chad Attermann [EMAIL PROTECTED] writes:
Running at least i486 code would make sense on AMD Opteron processors. I
am shocked that the gcc version shipped by Sun Microsystems would be
compiled for i386. I compiled my own version of gcc 4.2.2 n the same
platform and it too appears to have
Hello all. Late last year I posted a couple of questions about
multi-threaded application hangs in Solaris 10 for x86 platforms, and about
thread-safety of std::basic_string in general. This was an attempt to solve
persistent problems I have been experiencing with my application hanging due
Chad Attermann wrote:
Hello all. Late last year I posted a couple of questions about
multi-threaded application hangs in Solaris 10 for x86 platforms, and
about thread-safety of std::basic_string in general. This was an
attempt to solve persistent problems I have been experiencing with my
Chad Attermann [EMAIL PROTECTED] writes:
Hello all. Late last year I posted a couple of questions about
multi-threaded application hangs in Solaris 10 for x86 platforms, and
about thread-safety of std::basic_string in general. This was an
attempt to solve persistent problems I have been
Ian Lance Taylor [EMAIL PROTECTED] writes:
Chad Attermann [EMAIL PROTECTED] writes:
Hello all. Late last year I posted a couple of questions about
multi-threaded application hangs in Solaris 10 for x86 platforms, and
about thread-safety of std::basic_string in general. This was an
attempt
Chad Attermann [EMAIL PROTECTED] writes:
I can not confirm that it was the i386 code included in the gcc build
but it appears that way from the signature. Is this perhaps a problem
with the way that gcc 3.4.3 shipping with Solaris 10 x86 was built?
Should it have opted for the i486 version
