All of lore.kernel.org
 help / color / mirror / Atom feed
From: markus@trippelsdorf.de (Markus Trippelsdorf)
To: linux-arm-kernel@lists.infradead.org
Subject: Build failure with v4.9-rc1 and GCC trunk -- compiler weirdness
Date: Wed, 19 Oct 2016 17:56:58 +0200	[thread overview]
Message-ID: <20161019155658.GB4411@x4> (raw)
In-Reply-To: <CA+55aFzSi4V9ZYDfxvZNfz1ogngTywW5Q9U_vQq3v83+0wgPrA@mail.gmail.com>

On 2016.10.19 at 08:55 -0700, Linus Torvalds wrote:
> On Wed, Oct 19, 2016 at 8:37 AM, Markus Trippelsdorf
> <markus@trippelsdorf.de> wrote:
> >
> > This is a gcc bug, see:
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=72785
> 
> Well, in the meantime we apparently have to live with it. Unless Will
> is using some unreleased gcc version that nobody else is using and we
> can just ignore it?

Yes, he is using gcc-7 that is unreleased. (It will be released April
next year.) 

-- 
Markus

WARNING: multiple messages have this Message-ID (diff)
From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Will Deacon <will.deacon@arm.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@kernel.org>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	james.greenhalgh@arm.com,
	Gregory Clement <gregory.clement@free-electrons.com>,
	Stephen Boyd <sboyd@codeaurora.org>
Subject: Re: Build failure with v4.9-rc1 and GCC trunk -- compiler weirdness
Date: Wed, 19 Oct 2016 17:56:58 +0200	[thread overview]
Message-ID: <20161019155658.GB4411@x4> (raw)
In-Reply-To: <CA+55aFzSi4V9ZYDfxvZNfz1ogngTywW5Q9U_vQq3v83+0wgPrA@mail.gmail.com>

On 2016.10.19 at 08:55 -0700, Linus Torvalds wrote:
> On Wed, Oct 19, 2016 at 8:37 AM, Markus Trippelsdorf
> <markus@trippelsdorf.de> wrote:
> >
> > This is a gcc bug, see:
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=72785
> 
> Well, in the meantime we apparently have to live with it. Unless Will
> is using some unreleased gcc version that nobody else is using and we
> can just ignore it?

Yes, he is using gcc-7 that is unreleased. (It will be released April
next year.) 

-- 
Markus

  reply	other threads:[~2016-10-19 15:56 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-17 18:38 Build failure with v4.9-rc1 and GCC trunk -- compiler weirdness Will Deacon
2016-10-17 18:38 ` Will Deacon
2016-10-17 19:43 ` Ard Biesheuvel
2016-10-17 19:43   ` Ard Biesheuvel
2016-10-19 13:35   ` Will Deacon
2016-10-19 13:35     ` Will Deacon
2016-10-19 14:59     ` Ard Biesheuvel
2016-10-19 14:59       ` Ard Biesheuvel
2016-10-19 15:01       ` Ard Biesheuvel
2016-10-19 15:01         ` Ard Biesheuvel
2016-10-19 15:11         ` Arnd Bergmann
2016-10-19 15:11           ` Arnd Bergmann
2016-10-19 15:27           ` Ard Biesheuvel
2016-10-19 15:27             ` Ard Biesheuvel
2016-10-19 15:44             ` Arnd Bergmann
2016-10-19 15:44               ` Arnd Bergmann
2016-10-19 15:32           ` Gregory CLEMENT
2016-10-19 15:32             ` Gregory CLEMENT
2016-10-19 15:58     ` Russell King - ARM Linux
2016-10-19 15:58       ` Russell King - ARM Linux
2016-10-19 15:37 ` Markus Trippelsdorf
2016-10-19 15:37   ` Markus Trippelsdorf
2016-10-19 15:55   ` Linus Torvalds
2016-10-19 15:55     ` Linus Torvalds
2016-10-19 15:56     ` Markus Trippelsdorf [this message]
2016-10-19 15:56       ` Markus Trippelsdorf
2016-10-19 16:00       ` Ard Biesheuvel
2016-10-19 16:00         ` Ard Biesheuvel
2016-10-19 16:01       ` Linus Torvalds
2016-10-19 16:01         ` Linus Torvalds
2016-10-19 16:22         ` Will Deacon
2016-10-19 16:22           ` Will Deacon
2017-02-01 16:58           ` Laura Abbott
2017-02-01 16:58             ` Laura Abbott
2017-02-01 17:36             ` Ard Biesheuvel
2017-02-01 17:36               ` Ard Biesheuvel
2017-02-01 18:19               ` Ard Biesheuvel
2017-02-01 18:19                 ` Ard Biesheuvel
2017-02-01 19:04                 ` Joe Perches
2017-02-01 19:04                   ` Joe Perches
2017-02-01 19:31                   ` Ard Biesheuvel
2017-02-01 19:31                     ` Ard Biesheuvel
2017-02-01 19:49                     ` Joe Perches
2017-02-01 19:49                       ` Joe Perches
2017-02-01 19:53                       ` Ard Biesheuvel
2017-02-01 19:53                         ` Ard Biesheuvel
2017-02-01 20:34                         ` Joe Perches
2017-02-01 20:34                           ` Joe Perches
2017-02-01 21:11                           ` Ard Biesheuvel
2017-02-01 21:11                             ` Ard Biesheuvel
2017-02-02  9:02                   ` Peter Zijlstra
2017-02-02  9:02                     ` Peter Zijlstra
2017-02-01 21:50               ` Laura Abbott
2017-02-01 21:50                 ` Laura Abbott
2017-02-02  9:17                 ` Ard Biesheuvel
2017-02-02  9:17                   ` Ard Biesheuvel
2017-02-02 15:43                   ` Laura Abbott
2017-02-02 15:43                     ` Laura Abbott
2017-02-02 15:45                     ` Ard Biesheuvel
2017-02-02 15:45                       ` Ard Biesheuvel

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=20161019155658.GB4411@x4 \
    --to=markus@trippelsdorf.de \
    --cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.