public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jvdelisle 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 12:43:00 -0000 [thread overview] Message-ID: <20101102124300.8RJglESouokGN5NX05Ko7Q_CxehFDC0rdEc0jMxuFzM@z> (raw) In-Reply-To: <bug-46267-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46267 Jerry DeLisle <jvdelisle at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jvdelisle at gcc dot | |gnu.org --- Comment #1 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> 2010-11-02 12:43:13 UTC --- I see strerror used in two places: ./intrinsics/gerror.c: p = strerror (errno); ./io/unix.c: return strerror (errno); There seems to be some configury already in config.h.in for something here. Can we simply define _GNU_SOURCE to get strerror_r and then just use it?
next prev parent reply other threads:[~2010-11-02 12:43 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 ` jvdelisle at gcc dot gnu.org [this message] 2010-11-02 13:06 ` [Bug libfortran/46267] " redi at gcc dot gnu.org 2010-11-02 13:20 ` jb at gcc dot gnu.org 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=20101102124300.8RJglESouokGN5NX05Ko7Q_CxehFDC0rdEc0jMxuFzM@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: linkBe 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).