This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc 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] Memory fencing problem in pthread cancellation

From: Jeff Law <law at redhat dot com>
To: "Carlos O'Donell" <carlos at systemhalted dot org>
Cc: Roland McGrath <roland at hack dot frob dot com>, Rich Felker <dalias at aerifal dot cx>, libc-alpha at sourceware dot org
Date: Tue, 15 Jan 2013 15:34:49 -0700
Subject: Re: [PATCH] Memory fencing problem in pthread cancellation
References: <50F46969.1000305@redhat.com> <20130115035000.GV20323@brightrain.aerifal.cx> <50F4DE50.3070400@redhat.com> <50F56C4F.8020908@systemhalted.org>

On 01/15/2013 07:48 AM, Carlos O'Donell wrote:

There might previously have been a bootstrapping issue in requiring
a libgcc_s.so to link against because you can't have built all of
the dynamic pieces of gcc?

Circular dependencies in the build process would certainly be the most obvious concern. You'd think that after 20+ years we'd have figured out a better way to bootstrap the compiler + base system library. Cue screenshots of everyone running "make world" to build BSD on their Vaxen...

Jeff

References:
- [PATCH] Memory fencing problem in pthread cancellation
  - From: Jeff Law
- Re: [PATCH] Memory fencing problem in pthread cancellation
  - From: Rich Felker
- Re: [PATCH] Memory fencing problem in pthread cancellation
  - From: Jeff Law
- Re: [PATCH] Memory fencing problem in pthread cancellation
  - From: Carlos O'Donell

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