On Fri, 18 May 2012, Ian Lance Taylor wrote: > Joel Sherrill <joel.sherr...@oarcorp.com> writes: > > > On 05/18/2012 08:27 AM, Ian Lance Taylor wrote: > >> Ralf Corsepius<ralf.corsep...@rtems.org> writes: > >> > >>> I am not sure, but AFAICT, -pthread is Linux-specific. > >> It's not properly documented, but -pthread works on a number of hosts, > >> including Solaris, Darwin, FreeBSD, NetBSD, OpenBSD, AIX. > > Ian.. Is it better to make it a noop for RTEMS or fix the test > > infrastructure that is turning it on where it doesn't exist? > > Sorry to be vague, but I think it depends on whether the tests are > meaningful on RTEMS. If dg-require-effective-target pthread_h lets a > test run, then I suppose I think the -pthread option ought to work.
There's also the effective-target pthread... (Somewhat redundant, but FWIW it pre-dates the effective-target pthread_h.) Depending on how the affected maintainers stand on the "-pthread"-everywhere question, you might want to add that test-case constraint to the tests requiring and passing -pthread. brgds, H-P
