This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libfortran/47375] GETLOG not threadsafe, causes warnings/wrong-code with static linking
- From: "jakub at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 20 Jan 2011 13:30:22 +0000
- Subject: [Bug libfortran/47375] GETLOG not threadsafe, causes warnings/wrong-code with static linking
- Auto-submitted: auto-generated
- References: <bug-47375-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47375
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-01-20 13:30:11 UTC ---
You should certainly avoid getpwuid etc. if getpwuid_r is available, otherwise
you can't call reliably getlog etc. from !$omp parallel.
That said, the warning is correct, if users have illusion that if they link
-static the C library no dynamic linking will be used, they need to be told
they are wrong. The simple fix is don't use -static.