public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jb at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/46267] strerror() is not necessarily thread-safe
Date: Tue, 02 Nov 2010 13:20:00 -0000	[thread overview]
Message-ID: <20101102132000.QCrZ8EvO_yjT8InVtXsv9QrzrWAejs47U0JMaNRxq7I@z> (raw)
In-Reply-To: <bug-46267-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Janne Blomqvist <jb at gcc dot gnu.org> 2010-11-02 13:20:48 UTC ---
Well, if we want to use strerror_r() we'd have to either first undef
_GNU_SOURCE before we include string.h so that we get the POSIX version (but,
might this cause some other weird breakage?) or then we need to have versions
both for glibc and others. E.g.

#ifdef HAVE_STRERROR_R
#ifdef _GNU_SOURCE
// Use glibc strerror_r()
#else
// Use POSIX strerror_r()
#else
// Use strerror()
#endif


  parent reply	other threads:[~2010-11-02 13:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-02 11:17 [Bug libfortran/46267] New: " jb at gcc dot gnu.org
2010-11-02 12:43 ` [Bug libfortran/46267] " jvdelisle at gcc dot gnu.org
2010-11-02 13:06 ` redi at gcc dot gnu.org
2010-11-02 13:20 ` jb at gcc dot gnu.org [this message]
2010-11-02 13:41 ` jakub at gcc dot gnu.org
2011-01-20 15:14 ` jb at gcc dot gnu.org
2011-01-20 18:59 ` jb at gcc dot gnu.org
2011-01-21 17:37 ` jb at gcc dot gnu.org
2011-01-21 23:01 ` jb at gcc dot gnu.org
2011-01-22 21:10 ` jb at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20101102132000.QCrZ8EvO_yjT8InVtXsv9QrzrWAejs47U0JMaNRxq7I@z \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).