From: Peter Zijlstra <peterz@infradead.org>
To: Maxime Coquelin <maxime.coquelin@st.com>
Cc: Rasmus Villemoes <linux@rasmusvillemoes.dk>,
gong.chen@linux.intel.com, Ingo Molnar <mingo@kernel.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
tytso@mit.edu, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, kernel@stlinux.com, eric.paire@st.com
Subject: Re: [PATCH v3] bitops: Fix shift overflow in GENMASK macros
Date: Wed, 5 Nov 2014 17:44:54 +0100 [thread overview]
Message-ID: <20141105164454.GY3337@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <545A4682.2080302@st.com>
On Wed, Nov 05, 2014 at 04:47:14PM +0100, Maxime Coquelin wrote:
>
> On 11/05/2014 12:10 PM, Rasmus Villemoes wrote:
> >On Tue, Nov 04 2014, Maxime COQUELIN <maxime.coquelin@st.com> wrote:
> >
> >>-#define GENMASK(h, l) (((U32_C(1) << ((h) - (l) + 1)) - 1) << (l))
> >>-#define GENMASK_ULL(h, l) (((U64_C(1) << ((h) - (l) + 1)) - 1) << (l))
> >>+#define GENMASK(h, l) \
> >>+ ((~0UL >> (BITS_PER_LONG - ((h) - (l) + 1))) << (l))
> >>+
> >>+#define GENMASK_ULL(h, l) \
> >>+ ((~0ULL >> (BITS_PER_LONG_LONG - ((h) - (l) + 1))) << (l))
> >Slightly bikeshedding here, but may I suggest spelling it
> >
> > (((~0UL) << (l)) & (~0UL >> (BITS_PER_LONG - 1 - (h))))
> >
> >? This will ensure the arguments are expanded once each, and will, IMHO,
> >DTRT if/when l > h (namely, yield 0).
> That's a good point.
>
> Peter, what is your view?
I'm fine with that, feel free to post another version and I'll replace
v3.
next prev parent reply other threads:[~2014-11-05 16:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-04 10:58 [PATCH v3] bitops: Fix shift overflow in GENMASK macros Maxime COQUELIN
2014-11-04 13:27 ` Peter Zijlstra
2014-11-05 11:10 ` Rasmus Villemoes
2014-11-05 15:47 ` Maxime Coquelin
2014-11-05 16:44 ` Peter Zijlstra [this message]
2014-11-06 9:56 ` Maxime Coquelin
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=20141105164454.GY3337@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=eric.paire@st.com \
--cc=gong.chen@linux.intel.com \
--cc=kernel@stlinux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=maxime.coquelin@st.com \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=stable@vger.kernel.org \
--cc=tytso@mit.edu \
/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.