From: Meelis Roos <mroos@linux.ee>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Re: gcc crashes with general protection faults in 5.9.0-rc3-00091-ge28f0104343d
Date: Fri, 11 Sep 2020 16:44:57 +0300 [thread overview]
Message-ID: <95c6539f-1c32-5caa-ce0f-e4a5e9859c56@linux.ee> (raw)
In-Reply-To: <70778c21-8039-5011-e885-221c2cb06220@linux.ee>
Replying to myself:
>> This is 5.9.0-rc3-00091-ge28f0104343d on Lenovo t460s that has ran fine up to 5.8.0.
>
> Now I reproduced the same problem with 5.9.0-rc3 on a HP desktop with Core2Quad CPU. The call trace is very similar and it's crashing gcc again while compiling 5.9-rc4.
>
> But it seems 5.9-rc4 cures it here as well - whatever the reason might have been.
Nope, the reason was nondeterminism - it happened on the Core2Quad running 5.9-rc4 while trying to compile todays Linux from git.
--
Meelis Roos <mroos@linux.ee>
next prev parent reply other threads:[~2020-09-11 15:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 19:37 gcc crashes with general protection faults in 5.9.0-rc3-00091-ge28f0104343d Meelis Roos
2020-09-08 3:58 ` Meelis Roos
2020-09-08 12:25 ` Meelis Roos
2020-09-11 13:44 ` Meelis Roos [this message]
2020-09-14 11:14 ` gcc crashes with general protection faults in 5.9.0-rc5 Meelis Roos
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=95c6539f-1c32-5caa-ce0f-e4a5e9859c56@linux.ee \
--to=mroos@linux.ee \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).