[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <EF5E805C-FBEE-48CB-97D1-571DC6D9BDE1@zytor.com>
Date: Mon, 27 Jul 2015 17:35:43 -0700
From: "H. Peter Anvin" <hpa@...or.com>
To: Andy Lutomirski <luto@...capital.net>
CC: Andy Lutomirski <luto@...nel.org>,
Uros Bizjak <uros_bizjak1@....net>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
X86 ML <x86@...nel.org>, Uros Bizjak <ubizjak@...il.com>,
Ingo Molnar <mingo@...nel.org>
Subject: Re: ASM flags in general
However... perhaps we can do the flags stuff first? There are certainly a ton of changes we ought to do.
On July 27, 2015 4:58:29 PM PDT, Andy Lutomirski <luto@...capital.net> wrote:
>On Mon, Jul 27, 2015 at 4:56 PM, H. Peter Anvin <hpa@...or.com> wrote:
>> Sure... but now you have to wrap things in stac/clac. I'm not sure I
>see the point since the code is already pretty much optimal.
>
>Ick. I forgot about that.
>
>It would benefit all the users who aren't using the _ex functions,
>though. And, if there are enough of those, it just might be worth
>trying to postprocess object files to collapse adjacent stac and clac
>instances, or just to teach the alternatives code to nop them out if
>they're redundant.
>
>--Andy
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists