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: [gomp] thread-safe libgfortran (fixes PR fortran/14943 and fortran/21647)

From: Steve Kargl <sgk at troutmask dot apl dot washington dot edu>
To: Richard Henderson <rth at redhat dot com>, Jakub Jelinek <jakub at redhat dot com>, Thomas Koenig <Thomas dot Koenig at online dot de>, fortran at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org
Date: Fri, 7 Oct 2005 19:36:14 -0700
Subject: Re: [gomp] thread-safe libgfortran (fixes PR fortran/14943 and fortran/21647)
References: <20051006235329.GG8983@devserv.devel.redhat.com> <20051007201737.GA2635@twiddle.net> <20051008004755.GD22818@devserv.devel.redhat.com> <20051008021142.GA17630@redhat.com>

On Fri, Oct 07, 2005 at 07:11:42PM -0700, Richard Henderson wrote:
> On Fri, Oct 07, 2005 at 08:47:55PM -0400, Jakub Jelinek wrote:
> > What's wrong with this?  There are different locks.
> 
> I mis-read, clearly.
> 
> > Ok for gomp?
> 
> As far as I'm concered, it's ok now, even if there are further
> changes necessary.  There's no sense in carrying around a patch
> this large...

I agree with rth.

I'll still try to bootstrap your patch on {i386,amd64}-*-freebsd
and run some tests.  FreeBSD doesn't use glibc, so it may a good
of your locking.  I'll also rad through the patch.

-- 
Steve

References:
- [PATCH] (almost) thread-safe libgfortran
  - From: Jakub Jelinek
- Re: [PATCH] (almost) thread-safe libgfortran
  - From: Richard Henderson
- [gomp] thread-safe libgfortran (fixes PR fortran/14943 and fortran/21647)
  - From: Jakub Jelinek
- Re: [gomp] thread-safe libgfortran (fixes PR fortran/14943 and fortran/21647)
  - From: Richard Henderson

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