Thread starvation and resource saturation in atomicity functions?

2008-03-31 Thread Chad Attermann
read-priorities viable and safe. Thanks in advance for any insight, and at the very least I hope that this will serve as a warning to others who might find themselves in the same situation. Cheers, Chad Attermann

Re: Thread starvation and resource saturation in atomicity functions?

2008-03-31 Thread Chad Attermann
"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

Re: Thread starvation and resource saturation in atomicity functions?

2008-04-01 Thread Chad Attermann
"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.

Re: Thread starvation and resource saturation in atomicity functions?

2008-04-01 Thread Chad Attermann
"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 i