http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46267
Janne Blomqvist changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46267
--- Comment #8 from Janne Blomqvist 2011-01-21 22:42:26
UTC ---
Author: jb
Date: Fri Jan 21 22:42:17 2011
New Revision: 169110
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=169110
Log:
PR 46267 strerror thread safety
Modified:
trunk
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46267
Janne Blomqvist changed:
What|Removed |Added
URL|http://gcc.gnu.org/ml/gcc-p |http://gcc.gnu.org/ml/gcc-p
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46267
Janne Blomqvist changed:
What|Removed |Added
URL||http://gcc.gnu.org/ml/gcc-p
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46267
Janne Blomqvist changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46267
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #4 f
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46267
--- Comment #3 from Janne Blomqvist 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 b
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46267
--- Comment #2 from Jonathan Wakely 2010-11-02
13:06:22 UTC ---
(In reply to comment #1)
> Can we simply define _GNU_SOURCE to get strerror_r and then just use it?
What about non-glibc systems?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46267
Jerry DeLisle changed:
What|Removed |Added
CC||jvdelisle at gcc dot
|
