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

2016-07-16 Thread Andreas Schwab
Andrew Pinski writes: > 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.

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

2016-07-16 Thread Patrick Palka
On Sat, Jul 16, 2016 at 4:27 AM, Andreas Schwab wrote: > Andrew Pinski writes: > >> 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 m

Re: "error: static assertion failed: [...]"

2016-07-16 Thread Martin Sebor
From a diagnostics point-of-view, neither version is quoted: c/c-parser.c: error_at (assert_loc, "static assertion failed: %E", string); cp/semantics.c: error ("static assertion failed: %s", To be "quoted", it would need to use either %q or %<%>. Note that %qs would produce `foo' not "foo". Ne

Re: [RFC] Rationale for passing vectors by value in SIMD registers

2016-07-16 Thread Andrew Pinski
On Sat, Feb 15, 2014 at 12:16 AM, Matthew Fortune wrote: >> On Fri, Feb 14, 2014 at 2:17 AM, Matthew Fortune >> wrote: >> > MIPS is currently evaluating the benefit of using SIMD registers to pass >> vector data by value. It is currently unclear how important it is for vector >> data >> to be pa