On Thu, Jan 15, 2015 at 9:04 PM, Jeff Law <l...@redhat.com> wrote: > > Stage3 is closing rapidly. I've drained my queue of patches I was tracking > for gcc-5. However, note that I don't track everything. If it's a patch > for a backend, language other than C or seemingly has another maintainer > that's engaged in review, then I haven't been tracking the patch. > > So this is my final call for patch pings. I've got some bandwidth and may > be able to look at a few patches that have otherwise stalled.
I've been pinging this for about a year now in case it's of interest: https://gcc.gnu.org/ml/gcc-patches/2014-10/msg01871.html It fixes a show-stopper for using GOMP in libraries -- currently you cannot use GOMP in any code where you don't control the whole program, b/c it breaks fork(). (GOMP is the only OMP implementation that has this problem.) This is particularly annoying for Python, since it manifests as person A writing a fancy numerical package that happens to use OMP internally (b/c they don't know any better), and then person B trying to use Python's standard 'multiprocessing' library and getting weird hangs and having no idea why. -n -- Nathaniel J. Smith Postdoctoral researcher - Informatics - University of Edinburgh http://vorpus.org
