This is the mail archive of the
mailing list for the GCC project.
Re: Segmentation fault in openmp simple routine from libgomp testsuite.
- From: Andrew Pinski <pinskia at physics dot uc dot edu>
- To: FX Coudert <fxcoudert at gmail dot com>
- Cc: Jakub Jelinek <jakub at redhat dot com>, GCC Development <gcc at gcc dot gnu dot org>, Richard Henderson <rth at redhat dot com>, Diego Novillo <dnovillo at redhat dot com>, Fortran List <fortran at gcc dot gnu dot org>
- Date: Tue, 7 Mar 2006 18:31:52 -0500
- Subject: Re: Segmentation fault in openmp simple routine from libgomp testsuite.
- References: <email@example.com> <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org> <email@example.com> <440DC40D.firstname.lastname@example.org> <20060307191559.GA3652@redhat.com> <email@example.com>
On Mar 7, 2006, at 6:12 PM, FX Coudert wrote:
The only sure-fire fix I can think of is to actually build
two static versions of libgfortran -- one threaded and one
not threaded. I'm not sure this is worth the effort, really.
I'd be more inclined to put a couple of checks in such that
the static libgfortran only runs non-threaded, and force
people to use shared libgfortran for OpenMP.
Hum, there are some platforms where libgfortran (and other target
libraries) cannot be built as shared libraries. i386-mingw32 is an
example of that. We've been careful until now to keep static
libgfortran working even as a static library, and it would be a pity
not to be able to run OpenMP on this platform.
I bet the same issue now will happen with libstdc++ (and in 4.1.0 in
I want to say the weak references is the wrong way of doing things for