From: Alexander Tsoy <alexander@tsoy.me>
To: "Linus Torvalds" <torvalds@linux-foundation.org>,
"Toralf Förster" <toralf.foerster@gmx.de>
Cc: Andy Lutomirski <luto@amacapital.net>,
stable <stable@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
the arch/x86 maintainers <x86@kernel.org>
Subject: Re: 4.14.9 doesn't boot (regression)
Date: Sat, 30 Dec 2017 01:04:40 +0300 [thread overview]
Message-ID: <1514585080.28262.16.camel@tsoy.me> (raw)
In-Reply-To: <CA+55aFzeyHYXJKHFGqOt-R5fhMEuq8RTQLF=4=J=bwffo6mkgw@mail.gmail.com>
В Пт, 29/12/2017 в 13:39 -0800, Linus Torvalds пишет:
> On Fri, Dec 29, 2017 at 1:17 PM, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> >
> > Yeah, other reporters of this have used gcc-6.4.0 too.
> >
> > But there's been some muddying of the waters there too - changing
> > compilers have fixed it for some cases, but there's at least one
> > report that a kernel build with gcc-7.2.0 still had the issue (and
> > another that said it didn't).
>
> Side note: I'm not convinced that we will reliably catch a compiler
> version change in our dependency analysis, so it's probably best to
> "make clean" between switching compilers to make sure that you don't
> have old object files with the old compiler.
I did "make clean" after changing compiler flags.
next prev parent reply other threads:[~2017-12-29 22:04 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-29 11:14 4.14.9 doesn't boot (regression) Toralf Förster
2017-12-29 13:33 ` Sebastian Gottschall
2017-12-29 13:38 ` Toralf Förster
2017-12-29 15:29 ` Andy Shevchenko
2017-12-29 15:48 ` Alexander Tsoy
2017-12-29 15:52 ` Toralf Förster
2017-12-29 20:12 ` Linus Torvalds
2017-12-29 20:21 ` Ingo Molnar
2017-12-29 21:02 ` Toralf Förster
2017-12-29 21:17 ` Linus Torvalds
2017-12-29 21:39 ` Linus Torvalds
2017-12-29 22:04 ` Alexander Tsoy [this message]
2017-12-29 22:30 ` Toralf Förster
2017-12-29 22:53 ` Linus Torvalds
2017-12-29 23:14 ` Toralf Förster
2017-12-30 0:10 ` Andy Lutomirski
2017-12-30 1:00 ` Linus Torvalds
2017-12-30 1:34 ` Linus Torvalds
2017-12-30 9:14 ` Alexander Tsoy
2017-12-30 9:21 ` Toralf Förster
2017-12-30 1:13 ` Alexander Tsoy
2017-12-30 12:58 ` Toralf Förster
2017-12-30 13:14 ` Jiri Kosina
2017-12-30 3:49 ` Josh Poimboeuf
2017-12-30 8:45 ` Alexander Tsoy
2017-12-30 17:09 ` Josh Poimboeuf
2017-12-30 17:57 ` Josh Poimboeuf
2017-12-30 22:03 ` Alexander Tsoy
2017-12-30 22:16 ` Josh Poimboeuf
2017-12-30 9:30 ` Toralf Förster
2017-12-30 8:32 ` Toralf Förster
2017-12-30 9:53 ` Jiri Kosina
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=1514585080.28262.16.camel@tsoy.me \
--to=alexander@tsoy.me \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=stable@vger.kernel.org \
--cc=toralf.foerster@gmx.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@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