From: Borislav Petkov <bp@alien8.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>, Al Viro <viro@zeniv.linux.org.uk>,
Andy Lutomirski <luto@amacapital.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Andrew Morton <akpm@linux-foundation.org>,
Michael Matz <matz@suse.de>
Subject: Re: [GIT PULL] x86 cleanups for v5.7
Date: Thu, 2 Apr 2020 15:40:51 +0200 [thread overview]
Message-ID: <20200402134051.GC9352@zn.tnic> (raw)
In-Reply-To: <CAHk-=wh3_WTKeR=TTbPpbJYjC8DOPcDPJhhoopTVs3WJimsT=A@mail.gmail.com>
On Wed, Apr 01, 2020 at 05:16:24PM -0700, Linus Torvalds wrote:
> Nobody else has a working compiler to even test that patch, because
> even upstream tip-of-the-day llvm mis-generates code (I have a patch
> that makes it generate ok code, but that one isn't good enough to
> actually go upstream in llvm).
Btw, looking at this:
https://reviews.llvm.org/rG50cac248773
and talking to a gcc guy (CCed), it should be also relatively easy to do
the fallthrough variant in gcc too so you could open a feature request
for that in the gcc bugzilla.
HTH.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2020-04-02 13:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-31 8:01 [GIT PULL] x86 cleanups for v5.7 Ingo Molnar
2020-03-31 18:09 ` Linus Torvalds
2020-04-01 22:45 ` Linus Torvalds
2020-04-01 23:55 ` Thomas Gleixner
2020-04-02 0:16 ` Linus Torvalds
2020-04-02 8:19 ` Thomas Gleixner
2020-04-02 13:40 ` Borislav Petkov [this message]
2020-04-02 17:00 ` Linus Torvalds
2020-04-02 17:24 ` Borislav Petkov
2020-04-02 17:40 ` Linus Torvalds
2020-04-02 18:03 ` Borislav Petkov
2020-04-02 18:13 ` Linus Torvalds
2020-04-03 13:46 ` Jiri Kosina
2020-04-03 17:03 ` Linus Torvalds
2020-03-31 19:15 ` pr-tracker-bot
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=20200402134051.GC9352@zn.tnic \
--to=bp@alien8.de \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=matz@suse.de \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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.