From: David Miller <davem@davemloft.net>
To: glaubitz@physik.fu-berlin.de
Cc: wbx@openadk.org, linux-kernel@vger.kernel.org,
sparclinux@vger.kernel.org
Subject: Re: sparc gcc 7.1 compile issue
Date: Fri, 02 Jun 2017 10:22:59 -0400 (EDT) [thread overview]
Message-ID: <20170602.102259.363059784928463769.davem@davemloft.net> (raw)
In-Reply-To: <20170602091717.GA7452@physik.fu-berlin.de>
From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Date: Fri, 2 Jun 2017 11:17:18 +0200
> On Wed, May 31, 2017 at 05:10:08PM -0400, David Miller wrote:
>> A fix for this is in Linus's tree and was submitted to -stable last
>> night:
>
> What remains to be fixed though is that the gcc-7 testsuite
> *reproducibly* kills the kernel on sparc64 when building with more than
> around 20 jobs:
Well, I already have a release gcc bug to fix so pretty much I have no
time to look into bugs in unreleased versions of gcc sorry.
next prev parent reply other threads:[~2017-06-02 14:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 19:34 Waldemar Brodkorb
2017-05-31 21:10 ` David Miller
2017-06-01 12:12 ` Waldemar Brodkorb
2017-06-01 12:46 ` Anatoly Pugachev
2017-06-01 12:48 ` John Paul Adrian Glaubitz
2017-06-01 16:45 ` David Miller
2017-06-02 9:17 ` John Paul Adrian Glaubitz
2017-06-02 14:22 ` David Miller [this message]
2017-06-02 16:33 ` John Paul Adrian Glaubitz
2017-06-02 17:28 ` David Miller
2017-06-04 13:16 ` John Paul Adrian Glaubitz
2017-06-04 14:40 ` Waldemar Brodkorb
2017-06-04 15:09 ` John Paul Adrian Glaubitz
2017-06-04 20:22 ` David Miller
2017-06-04 20:27 ` John Paul Adrian Glaubitz
2017-06-04 20:21 ` David Miller
2017-06-04 20:26 ` John Paul Adrian Glaubitz
2017-06-04 20:30 ` David Miller
2017-06-04 20:33 ` John Paul Adrian Glaubitz
2017-06-04 20:34 ` David Miller
2017-06-04 20:38 ` John Paul Adrian Glaubitz
2017-06-18 9:22 ` Pavel Machek
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=20170602.102259.363059784928463769.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@vger.kernel.org \
--cc=wbx@openadk.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
all inboxes | Powered by JetHome®