From: Michal Januszewski <michalj@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Rolf Eike Beer <eike-kernel@sf-tec.de>,
linux-kernel@vger.kernel.org,
Linux Fbdev development list <linux-fbdev@vger.kernel.org>
Subject: Re: abs() vs. abs64() (was: Re: [PATCH] fbdev: fix nearest mode
Date: Fri, 19 Nov 2010 22:28:23 +0000 [thread overview]
Message-ID: <20101119222823.GA28797@quadria> (raw)
In-Reply-To: <20101119140721.33576c61.akpm@linux-foundation.org>
On Fri, Nov 19, 2010 at 02:07:21PM -0800, Andrew Morton wrote:
> On Thu, 18 Nov 2010 07:40:19 +0100
> Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> > > 'c' will end up with a value of 0xffffffff instead of the expected 0x1.
> >
> > This happens on 64-bit only, right?
Absolutely, I should have mentioned it in the patch description.
> How does this look?
>
> [..]
>
> Reported-by: Michal Januszewski <michalj@gmail.com>
> Cc: Rolf Eike Beer <eike-kernel@sf-tec.de
> Cc: Geert Uytterhoeven <geert@linux-m68k.org>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
>
> include/linux/kernel.h | 13 ++++++++++---
> 1 file changed, 10 insertions(+), 3 deletions(-)
>
> diff -puN include/linux/kernel.h~include-linux-kernelh-abs-fix-handling-of-32-bit-unsigneds-on-64-bit include/linux/kernel.h
> --- a/include/linux/kernel.h~include-linux-kernelh-abs-fix-handling-of-32-bit-unsigneds-on-64-bit
> +++ a/include/linux/kernel.h
> @@ -143,9 +143,16 @@ extern int _cond_resched(void);
>
> #define might_sleep_if(cond) do { if (cond) might_sleep(); } while (0)
>
> -#define abs(x) ({ \
> - long __x = (x); \
> - (__x < 0) ? -__x : __x; \
> +#define abs(x) ({ \
> + long ret; \
> + if (sizeof(x) = sizeof(long)) { \
> + long __x = (x); \
> + ret = (__x < 0) ? -__x : __x; \
> + } else { \
> + int __x = (x); \
> + ret = (__x < 0) ? -__x : __x; \
> + } \
> + ret; \
> })
>
> #define abs64(x) ({ \
> _
Looks good to me. I posted essentially the same thing some 3 months ago
(http://marc.info/?l=linux-kernel&m\x128033094822201&w=2) but it then
failed to get any traction. At any rate, I like your version better as
it seems more readable.
Michal
next prev parent reply other threads:[~2010-11-19 22:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-18 6:40 abs() vs. abs64() (was: Re: [PATCH] fbdev: fix nearest mode search) Geert Uytterhoeven
2010-11-19 22:07 ` abs() vs. abs64() (was: Re: [PATCH] fbdev: fix nearest mode Andrew Morton
2010-11-19 22:28 ` Michal Januszewski [this message]
2010-11-19 23:04 ` Andrew Morton
2010-11-19 23:19 ` Andrew Morton
2010-11-20 8:56 ` abs() vs. abs64() (was: Re: [PATCH] fbdev: fix nearest mode search) Geert Uytterhoeven
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=20101119222823.GA28797@quadria \
--to=michalj@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=eike-kernel@sf-tec.de \
--cc=geert@linux-m68k.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).