From fcf462eb5d280aa3cbc0b1b35c20c91b57b4e6dc Mon Sep 17 00:00:00 2001 From: Eelco Dolstra Date: Mon, 16 Dec 2013 21:43:27 +0100 Subject: [PATCH] gcc: Disable profiled build This can fail randomly with an error like: building toplev.o ../../gcc-4.6.3/gcc/reload.c: In function 'find_reloads': ../../gcc-4.6.3/gcc/reload.c:3778:11: error: corrupted value profile: value profile counter (93791 out of 95865) inconsistent with basic-block count (95759) http://hydra.nixos.org/build/7185029 On the plus side, this makes building GCC much faster because it re-enables parallel building. --- pkgs/top-level/all-packages.nix | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pkgs/top-level/all-packages.nix b/pkgs/top-level/all-packages.nix index 4d0365b22e3c..507ec8857a6b 100644 --- a/pkgs/top-level/all-packages.nix +++ b/pkgs/top-level/all-packages.nix @@ -2358,7 +2358,7 @@ let # bootstrapping a profiled compiler does not work in the sheevaplug: # http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43944 - profiledCompiler = !stdenv.isArm; + profiledCompiler = false; # When building `gcc.crossDrv' (a "Canadian cross", with host == target # and host != build), `cross' must be null but the cross-libc must still