This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/44927] static linkage with -lgomp fails on simple program
- From: "kargl at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 16 Jul 2010 14:48:25 -0000
- Subject: [Bug fortran/44927] static linkage with -lgomp fails on simple program
- References: <bug-44927-19433@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #11 from kargl at gcc dot gnu dot org 2010-07-16 14:48 -------
(In reply to comment #10)
> (In reply to comment #9)
> > (In reply to comment #6)
> > > Please don't keep reopening this bug.
> > > The symbols are weak undefs because libgfortran doesn't require (and shouldn't
> > > require) libpthread, it is thread-safe only when libpthread is linked in.
> > >
> >
> > After reviewing the thread (and recalling others along this line),
> > Jakub, if you want to make the combination of -static -fopenmp
> > a fatal error for gfortran, a patch is pre-approved.
>
> I am against it - if you "properly" link it, e.g. using -Wl,--whole-archive or
> with a POSIX Threads (pthread) library, which is linked with "ld -r", it works.
I don't see this in the information in the gfortran documentation.
> That's a similar issue to -m(no-)align-double: It leads to difficult to
> understand crashes, but it is nontrivial to diagnose properly as there are
> valid/working combinations - even though most combinations lead to crashes.
Well, I would like to disable the use of -malign-double on gfortran
as well.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44927