[Bug libgomp/46592] New: -ftree-parallelize-loops attempts to link pthreads on non-posix systems

[Bug libgomp/46592] New: -ftree-parallelize-loops attempts to link pthreads on non-posix systems

[green at redhat dot com]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46592

           Summary: -ftree-parallelize-loops attempts to link pthreads on
                    non-posix systems
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libgomp
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: green@redhat.com


*-elf toolchains are failing the -ftree-parallelize-loops test pr46111 because
using that option unconditionally attempts to link pthreads.  I suppose I could
define GOMP_SELF_SPECS to "" for my target, but why isn't pthreads only linked
in with libgomp is linked?

[Bug libgomp/46592] -ftree-parallelize-loops attempts to link pthreads on non-posix systems

[jakub at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46592

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> 2010-11-21 14:34:51 UTC ---
Testing -ftree-parallelize-loops on targets which don't have threads doesn't
make any sense, for C -ftree-parallelize-loops=N tests are all in
gcc.dg/autopar/ which is guarded by
if ![check_effective_target_pthread] {
  return
}
perhaps just the test needs
// { dg-require-effective-target pthread }
or we need g++.dg/autopar/
which will be guarded similarly.