From: Thomas Gleixner <tglx@linutronix.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: 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>,
Borislav Petkov <bp@alien8.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] x86 cleanups for v5.7
Date: Thu, 02 Apr 2020 10:19:40 +0200 [thread overview]
Message-ID: <87sghmnvtv.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <CAHk-=wh3_WTKeR=TTbPpbJYjC8DOPcDPJhhoopTVs3WJimsT=A@mail.gmail.com>
Linus Torvalds <torvalds@linux-foundation.org> writes:
> On Wed, Apr 1, 2020 at 4:55 PM Thomas Gleixner <tglx@linutronix.de> wrote:
>>
>> - x86 starts the short log after the colon with an uppercase
>> letter
>
> Ahh. I actually tried to match the previous ones by Al, and they don't
> follow that pattern.
Yeah. As Al's stuff was late already, I just took it as is.
>> - All commits lack a Link:https//lore.kernel.org/r/$MSG-ID tag. That
>> might be an oversight or just reflecting the fact that these patches
>> have never seen a mailing list.
>
> Yeah. They were literally me looking at my patch in my other tree, and
> trying to make incremental progress.
>
> 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).
Fair enough.
> I don't think I'll do any more, because the next stage really is to
> actually have some CONFIG_ASM_GOTO_WITH_INPUTS code and then try to
> make something similar to the SET_CC for this.
>
>> From a quick check I can confirm that the resulting text changes are
>> just random noise and I did not notice anything horrible in the
>> generated code either.
>
> Btw, do you guys have some better object code comparison thing than my
> "objdump plus a few sed scripts to hide code movement effects"
Not sure whether s/sed/python/ makes it any better :)
Thanks,
tglx
next prev parent reply other threads:[~2020-04-02 8:19 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 [this message]
2020-04-02 13:40 ` Borislav Petkov
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=87sghmnvtv.fsf@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).