1 |
Hello, |
2 |
|
3 |
On Thu, 24 Dec 2015, Alan Grimes wrote: |
4 |
>Hey, thanks for putting out gcc 5.3... |
5 |
> |
6 |
>Unfortunately, it fails to bootstrap on my machine. I am getting |
7 |
>differences between the stage 2 and stage 3 compilers and it's dying... =( |
8 |
|
9 |
What compiler and C(XX)FLAGS are you using? It builds nicely with |
10 |
gcc-4.9 (and rather agressive flags) here. With how many processes |
11 |
(MAKEOPTS) are you compiling?. |
12 |
|
13 |
Also, compiling gcc might expose flaky RAM (removing and reseating the |
14 |
RAM DIMMs might help there[0]). Have you e.g. encoded stuff with |
15 |
mencoder or ffmpeg lately[1]? If you're compiling with any MAKEOPTS |
16 |
'-j1' it could be the same phenomenon as I had in [1], so try with |
17 |
-j1. If that works ... Consider using prime95/mprime[2] for a test. |
18 |
|
19 |
-dnh |
20 |
|
21 |
[0] stuff expands and shrinks depending on temps, so connections can |
22 |
get flaky even if the box isn't moved ;) |
23 |
|
24 |
[1] I've had mencoder segfault on me reproducibly on one box after |
25 |
20-30 mins encoding with one process, and <= 10mins with two |
26 |
processes. Memtest86 found nothing in one round. New RAM (replaced |
27 |
on guarantee :) cured the problem for good. |
28 |
|
29 |
[2] http://www.mersenne.org/download/#download |
30 |
|
31 |
-- |
32 |
panic("Attempted to kill the idle task!"); |
33 |
linux-2.2.16/kernel/exit.c |