This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/47571] [4.7 Regression] undefined reference to clock_gettime in Linux build of 02/01/2011
- From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 21 Mar 2011 16:49:55 +0000
- Subject: [Bug fortran/47571] [4.7 Regression] undefined reference to clock_gettime in Linux build of 02/01/2011
- Auto-submitted: auto-generated
- References: <bug-47571-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47571
--- Comment #47 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> 2011-03-21 16:49:19 UTC ---
> --- Comment #46 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-03-21 16:34:39 UTC ---
> You clearly don't understand that linking librt in means linking both librt and
> libpthread in, thus both some overhead at the start of application, for various
> places in the C library that behave differently if libpthread is linked in, and
> even gthr* suddenly is more costly just because librt has been linked in.
Of course I do, I was just asking for what the actual overhead is.
> I think on a target which doesn't support weaks having GFORTRAN_USE_WEAK
> defined to 1 is just wrong.
No, this target (and others) do support weak, just not weakrefs. The
macros should reflect their meaning (SUPPORTS_WEAKREF) and have all
necessary knowledge in one place (acinclude.m4) instead of playing games
with both SUPPORTS_WEAK and GTHREAD_USE_WEAK.
Rainer