From: John David Anglin <dave.anglin@bell.net>
To: Meelis Roos <mroos@linux.ee>, linux-parisc@vger.kernel.org
Subject: Re: 4.12-rc5+: segfault while compiling, on rp3410
Date: Tue, 20 Jun 2017 12:11:51 -0400 [thread overview]
Message-ID: <d2f4c409-16db-7dbb-533f-c7e56515bceb@bell.net> (raw)
In-Reply-To: <alpine.LRH.2.20.1706201714280.12869@math.ut.ee>
On 2017-06-20 10:20 AM, Meelis Roos wrote:
> I am using gentoo on my hppa machines and just tried
> 4.12.0-rc5-00187-gab2789b at the end of last week. This time there
> was new gcc release so a lot of work. rp3440 and A500 had no problems,
> rp3410 errored out with SIGSEGV, twice.
Helge and I have had a long discussion about these SEGVs. They are
essentially random.
The are very rare on UP machines. I don't think we have seen one yet on
the panama buildd
machine which is also a rp3410. They are much more common on phantom
which is four way
c8000 at 1 GHz.
Dave
--
John David Anglin dave.anglin@bell.net
next prev parent reply other threads:[~2017-06-20 16:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-20 14:20 4.12-rc5+: segfault while compiling, on rp3410 Meelis Roos
2017-06-20 16:11 ` John David Anglin [this message]
2017-06-22 7:32 ` Meelis Roos
2017-07-03 7:38 ` 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=d2f4c409-16db-7dbb-533f-c7e56515bceb@bell.net \
--to=dave.anglin@bell.net \
--cc=linux-parisc@vger.kernel.org \
--cc=mroos@linux.ee \
/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