This is the mail archive of the
mailing list for the GCC project.
Re: [RFC] Old school parallelization of WPA streaming
- From: Richard Biener <rguenther at suse dot de>
- To: Michael Matz <matz at suse dot de>
- Cc: Andi Kleen <ak at linux dot intel dot com>, Jan Hubicka <hubicka at ucw dot cz>, gcc-patches at gcc dot gnu dot org, dnovillo at google dot com, dmalcolm at redhat dot com
- Date: Thu, 29 Aug 2013 09:33:51 +0200 (CEST)
- Subject: Re: [RFC] Old school parallelization of WPA streaming
- Authentication-results: sourceware.org; auth=none
- References: <20130821141747 dot GD24782 at kam dot mff dot cuni dot cz> <20130821145853 dot GB2139 at tassilo dot jf dot intel dot com> <aa686933-7ae6-461b-9403-d5d47ad11289 at email dot android dot com> <alpine dot LNX dot 2 dot 00 dot 1308281728110 dot 9949 at wotan dot suse dot de>
On Wed, 28 Aug 2013, Michael Matz wrote:
> On Wed, 21 Aug 2013, Richard Biener wrote:
> > I also fail to see why threads should not work here. Maybe simply
> > annotate gcc with openmp?
> Threads simply don't work here, because the whole streamer infrastructure
> (or anything else in GCC for that matter) isn't thread safe (you'd have to
> have multiple streamer objects, multiple SCC finder objects, and you'd
> have to audit everything for not using any other shared resources).
Hm, yeah, of course.
> Fork-fire-forget is really a much simpler choice here IMO; no worries
> about shared resources, less debug hassle.
It might be not as cheap as it is on Linux hosts on other hosts of
course. Also I'd rather try to avoid I/O than solving the issue
by parallelizing it. Of course we can always come back to this
kind of hack later.