public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@suse.de>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Ingo Molnar <mingo@kernel.org>,
	ling.ma.program@gmail.com, mingo@redhat.com, tglx@linutronix.de,
	linux-kernel@vger.kernel.org, Ma Ling <ling.ml@alipay.com>
Subject: Re: [Suggestion] [x86]: Compiler Option Os is better on latest x86
Date: Thu, 24 Jan 2013 16:25:44 +0100	[thread overview]
Message-ID: <20130124152544.GA13504@pd.tnic> (raw)
In-Reply-To: <51014B9A.5080500@zytor.com>

On Thu, Jan 24, 2013 at 08:56:26AM -0600, H. Peter Anvin wrote:
> There has been occasional talk about a -Ok(ernel) option to gcc, but
> that would require someone to go through gcc and figure out what bits
> makes sense and which don't...

Yep, such an option has a great potential for us and, if done right,
would be very cool. It could probably be taught to insert HWEIGHT,
RDRAND, CLFLUSH and whatever other insns we have the inline asm versions
for... and query CPUID before that... uuh, nice stuff.

The alternative would be to fork gcc and call it kcc...

/me runs away pretty quickly without even turning back :-)

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--

  reply	other threads:[~2013-01-24 15:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-26  6:32 [Suggestion] [x86]: Compiler Option Os is better on latest x86 ling.ma.program
2013-01-24 14:17 ` Ingo Molnar
2013-01-24 14:46   ` Borislav Petkov
2013-01-24 14:56     ` H. Peter Anvin
2013-01-24 15:25       ` Borislav Petkov [this message]
2013-01-24 15:35         ` H. Peter Anvin
     [not found] <1356939140-4113-1-git-send-email-ling.ma@alipay.com>
2012-12-31  7:52 ` Ling Ma

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=20130124152544.GA13504@pd.tnic \
    --to=bp@suse.de \
    --cc=hpa@zytor.com \
    --cc=ling.ma.program@gmail.com \
    --cc=ling.ml@alipay.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    /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