public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan Grimes <ALONZOTG@verizon.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Gcc 5.3
Date: Fri, 25 Dec 2015 11:01:42 -0500	[thread overview]
Message-ID: <567D6866.3090607@verizon.net> (raw)
In-Reply-To: <20151224201755.GA32457@grusum.endjinn.de>

David Haller wrote:
> Hello,
>
> On Thu, 24 Dec 2015, Alan Grimes wrote:
>> Hey, thanks for putting out gcc 5.3...
>>
>> Unfortunately, it fails to bootstrap on my machine. I am getting
>> differences between the stage 2 and stage 3 compilers and it's dying... =(
> What compiler and C(XX)FLAGS are you using? It builds nicely with
> gcc-4.9 (and rather agressive flags) here. With how many processes
> (MAKEOPTS) are you compiling?.

6, one per core, because it doesn't go to 100% utilization, I can
continue to use the machine normally for desktop.

> Also, compiling gcc might expose flaky RAM (removing and reseating the
> RAM DIMMs might help there[0]). Have you e.g. encoded stuff with
> mencoder or ffmpeg lately[1]? If you're compiling with any MAKEOPTS
> '-j1' it could be the same phenomenon as I had in [1], so try with
> -j1. If that works ... Consider using prime95/mprime[2] for a test.

Been through that, I'm fairly confident with the integrity of the
machine right now.

> -dnh
>
> [0] stuff expands and shrinks depending on temps, so connections can
>     get flaky even if the box isn't moved ;)
>
> [1] I've had mencoder segfault on me reproducibly on one box after
>     20-30 mins encoding with one process, and <= 10mins with two
>     processes. Memtest86 found nothing in one round. New RAM (replaced
>     on guarantee :) cured the problem for good.
>
> [2] http://www.mersenne.org/download/#download


-- 
IQ is a measure of how stupid you feel.

Powers are not rights.



  reply	other threads:[~2015-12-25 16:02 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-24 15:18 [gentoo-user] Gcc 5.3 Alan Grimes
2015-12-24 15:39 ` Stanislav Nikolov
2015-12-24 16:05   ` Alan Grimes
2015-12-24 20:17 ` David Haller
2015-12-25 16:01   ` Alan Grimes [this message]
2015-12-24 22:05 ` Paul Colquhoun
2015-12-25 12:47 ` Andreas K. Huettel
2015-12-25 15:42   ` Alan Grimes
2015-12-25 20:40 ` [gentoo-user] " walt
2015-12-26  3:00   ` Paul Colquhoun
2015-12-26  5:44     ` Paul Colquhoun
2016-01-01 15:51       ` Stefan G. Weichinger
2015-12-26  6:25   ` David Haller
2015-12-26  8:40   ` Philip Webb
2015-12-28  8:17   ` Andrew Savchenko
2015-12-29 12:52     ` lee
2015-12-29 14:54       ` David Haller
2015-12-29 18:21         ` lee
2015-12-29 22:48           ` Neil Bothwick
2015-12-30 16:32             ` lee
2015-12-30 22:33               ` Paul Colquhoun
2016-01-01 10:37                 ` lee

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=567D6866.3090607@verizon.net \
    --to=alonzotg@verizon.net \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox