Re: Should the build system use ar rcs instead of ranlib + ar rc?

On Fri, Jul 15, 2016 at 6:46 PM, Patrick Palka wrote: > The build step that invokes "ranlib libbackend.a" (which immediately > follows the invocation of "ar rc libbackend.a ...") takes over 7 seconds > on my machine and causes the entire 450MB archive to be rewritten. By > instead making the buil

Should the build system use ar rcs instead of ranlib + ar rc?

The build step that invokes "ranlib libbackend.a" (which immediately follows the invocation of "ar rc libbackend.a ...") takes over 7 seconds on my machine and causes the entire 450MB archive to be rewritten. By instead making the build system use ar rcs -- so that the archive and its index are bu

Re: [gimplefe] hacking pass manager

On Sun, Jul 10, 2016 at 6:13 PM, Prasad Ghangal wrote: > On 8 July 2016 at 13:13, Richard Biener wrote: >> On Thu, Jul 7, 2016 at 9:45 PM, Prasad Ghangal >> wrote: >>> On 6 July 2016 at 14:24, Richard Biener wrote: On Wed, Jul 6, 2016 at 9:51 AM, Prasad Ghangal wrote: > On 30 J

GCC testsuite maintenance (was: [PATCH] Fix OpenACC vector_length parsing in fortran)

Hi! Including in case others also have opinions on "GCC testsuite maintenance". On Fri, 15 Jul 2016 10:21:13 +0200, Jakub Jelinek wrote: > On Fri, Jul 15, 2016 at 09:44:25AM +0200, Thomas Schwinge wrote: > > Does that me we (erroneously) accept any random junk after [...] > > No. The thing is

Re: Error building GCC 6.1.0 libstdc++

On 15 July 2016 at 00:45, Patrick Oppenlander wrote: > Hi, > > I'm running into a build problem when building GCC 6.1.0: > > > /home/patrick/src/e7/toolchain/build/gcc-6.1.0-stage2/./gcc/xgcc > -shared-libgcc -B/home/patrick/src/e7/toolchain/build/gcc-6.1.0-stage2/./gcc > -nostdinc++ > -L/home/patr