> On Dec 29, 2014, at 2:01 PM,
> wrote:
>
> I would bug this but bugz says to report things under “bootstrap” only if
> they are long lived failures, and I don’t know if this is.
>
> Just tried to build on my Mac OS 10.10 system, plain native build. It fails
> in libgcc2 due to stdio.h not
I would bug this but bugz says to report things under “bootstrap” only if they
are long lived failures, and I don’t know if this is.
Just tried to build on my Mac OS 10.10 system, plain native build. It fails in
libgcc2 due to stdio.h not found. A cross-build from the same source tree
(pdp11
On 29 December 2014 at 15:34, Ed Smith-Rowland wrote:
> The note on C++14 conformance referred to is not the place for this but: is
> our C++11 support really less tested and more experimental than our C++03
> support at this point? One thing I can think of might be gcc bootstrap.
The main differ
On 12/27/2014 08:03 PM, Jonathan Wakely wrote:
On 28 December 2014 at 00:08, Olaf van der Spek wrote:
On 26-12-2014 1:52, Jonathan Wakely wrote:
On 25 December 2014 at 16:28, Olaf van der Spek wrote:
Hi,
https://gcc.gnu.org/ links to https://gcc.gnu.org/gcc-5/ (GCC 5 C++14
language feature-c
