This is the mail archive of the fortran@gcc.gnu.org mailing list for the GNU Fortran project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [Patch, libfortran] PR47375 GETLOG thread safety

From: Tobias Burnus <burnus at net-b dot de>
To: Rainer Orth <ro at CeBiTec dot Uni-Bielefeld dot DE>
Cc: Janne Blomqvist <blomqvist dot janne at gmail dot com>, Fortran List <fortran at gcc dot gnu dot org>, GCC Patches <gcc-patches at gcc dot gnu dot org>
Date: Thu, 27 Jan 2011 15:53:00 +0100
Subject: Re: [Patch, libfortran] PR47375 GETLOG thread safety
References: <AANLkTinQU9K2HTSi6TgEgRmhVnNqW=cpb=PzaoqzB5yZ@mail.gmail.com> <ydd8vy6l88j.fsf@manam.CeBiTec.Uni-Bielefeld.DE>

On 01/27/2011 03:41 PM, Rainer Orth wrote:

the attached patch makes the GETLOG intrinsic thread safe by using the
POSIX getpwuid_r() function, if available.

This patch broke Solaris bootstrap:

The problem is that<pwd.h>  declares two different variants of
getpwuid_r:

I have filled a tracking bug: PR 47491.

And I have a question to you, Rainer: There are similar patches for ctime_r and for ttyname_r. Do they work as is on Solaris or is also special care required?

See: http://gcc.gnu.org/ml/fortran/2011-01/msg00225.html and http://gcc.gnu.org/ml/fortran/2011-01/msg00224.html

Tobias

Follow-Ups:
- Re: [Patch, libfortran] PR47375 GETLOG thread safety
  - From: Rainer Orth

References:
- [Patch, libfortran] PR47375 GETLOG thread safety
  - From: Janne Blomqvist
- Re: [Patch, libfortran] PR47375 GETLOG thread safety
  - From: Rainer Orth

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]