mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Borislav Petkov <borislav.petkov@amd.com>,
	mingo@kernel.org, linux-kernel@vger.kernel.org,
	frank.arnold@amd.com, akpm@linux-foundation.org,
	tglx@linutronix.de, linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/mce] x86/bitops: Move BIT_64() for a wider use
Date: Wed, 23 May 2012 19:11:25 +0200	[thread overview]
Message-ID: <20120523171125.GD18284@liondog.tnic> (raw)
In-Reply-To: <CA+55aFx_e6hS0F++kkNj9uDr-qtr-DE_R25Owb80DyZN+xixDA@mail.gmail.com>

On Wed, May 23, 2012 at 09:57:47AM -0700, Linus Torvalds wrote:
> On Wed, May 23, 2012 at 9:53 AM, Borislav Petkov <bp@alien8.de> wrote:
> >
> > How about the following completely untested chunk:
> 
> No, you can't do that. All standard C operations will return *one*
> type. That very much includes the ternary ?: operator.

And, in addition, hpa's example won't work too:

	u64 msr = ~BIT(1);

> The *only* ways I know of to get two types are
> 
>  - C preprocessor stuff, ie
> 
>      #define BIT(x)  __BIT_##x
> 
>    and then just enumerate all the 64 cases. This is portable, but it gets old.

Nah, that's ugly.

>  - using __builtin_choose_expr(), which actually allows the two
> expressions to have different types, but requires a very strict
> compile-time constant (ie you cannot rely on the optimizer making it a
> constant - because it needs to choose the expression before the
> optimizer runs)
> 
> There might be some other magic gcc extension, of course.

Hmm and if not, it looks like BIT_64 is the easiest and most readable
thing we can do.

Oh well.

-- 
Regards/Gruss,
    Boris.

  reply	other threads:[~2012-05-23 17:11 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-22 10:53 [PATCH 1/2] x86, bitops: Move BIT_64 " Borislav Petkov
2012-05-22 10:53 ` [PATCH 2/2] x86, MCE: Fix 32-bit build Borislav Petkov
2012-05-23 16:08   ` [tip:x86/mce] x86/mce: " tip-bot for Borislav Petkov
2012-05-23 16:18     ` Peter Zijlstra
2012-05-23 16:23       ` Borislav Petkov
2012-05-23 16:31         ` Peter Zijlstra
2012-05-23 16:44           ` Borislav Petkov
2012-05-23 16:46             ` Peter Zijlstra
2012-05-23 16:54               ` Borislav Petkov
2012-05-23 16:07 ` [tip:x86/mce] x86/bitops: Move BIT_64() for a wider use tip-bot for Borislav Petkov
2012-05-23 16:10   ` Peter Zijlstra
2012-05-23 16:11     ` H. Peter Anvin
2012-05-23 16:19       ` Borislav Petkov
2012-05-23 16:29         ` Peter Zijlstra
2012-05-23 16:31           ` H. Peter Anvin
2012-05-23 16:43             ` Linus Torvalds
2012-05-23 16:47               ` H. Peter Anvin
2012-05-23 16:50                 ` H. Peter Anvin
2012-05-23 16:54                 ` Linus Torvalds
2012-05-23 16:55                   ` H. Peter Anvin
2012-05-23 16:53             ` Borislav Petkov
2012-05-23 16:57               ` Linus Torvalds
2012-05-23 17:11                 ` Borislav Petkov [this message]
2012-05-23 17:37                   ` Linus Torvalds
2012-05-23 16:54           ` Peter Zijlstra
2012-05-23 16:40         ` Linus Torvalds
2012-05-23 16:42           ` H. Peter Anvin
2012-05-23 16:45             ` Linus Torvalds

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=20120523171125.GD18284@liondog.tnic \
    --to=bp@alien8.de \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=borislav.petkov@amd.com \
    --cc=frank.arnold@amd.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®