mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Satyam Sharma" <satyam.sharma@gmail.com>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: "Jarek Poplawski" <jarkao2@o2.pl>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, "Oleg Nesterov" <oleg@tv-sign.ru>
Subject: Re: [PATCH -mm] timer: parenthesis fix in tbase_get_deferrable() etc.
Date: Thu, 10 May 2007 13:56:27 +0530	[thread overview]
Message-ID: <a781481a0705100126x6a649c16ic26409b4ffe80ed3@mail.gmail.com> (raw)
In-Reply-To: <653FFBB4508B9042B5D43DC9E18836F55DFC44@scsmsx415.amr.corp.intel.com>

> >> >> >  static inline unsigned int
> >tbase_get_deferrable(tvec_base_t *base)
> >> >> >  {
> >> >> > -  return ((unsigned int)(unsigned long)base &
> >> >TBASE_DEFERRABLE_FLAG);
> >> >> > +  return (unsigned int)((unsigned long)base &
> >> >TBASE_DEFERRABLE_FLAG);
> >> >> >  }
> >> >...
> >> >> The change makes sense, but does it actually "fix" anything?
> >> >>
> >> >
> >> >Yes - this first place fixes logical error, so it's a sin
> >> >- even if not punishable in practice. (It's also unnecessary
> >> >test for long to int conversion.)
> >> >
> >>
> >> I am sorry, I don't understand. What is the logical error in
> >the first
> >> one?
> >>
> >> Actually, your change makes it different from what was originally
> >> indended.
> >> Original intention was to type convert base to a 32 bit value and
> >> bitwise& with FLAG.
> >
> >But that is not what the original code is doing. If you wanted to
> >typecast "base" to "a 32 bit value" then you should've used u32
> >instead.
> >
> >Anyway, if you originally intended to actually typecast "base" to
> >unsigned int, then you could do that directly without typecasting it
> >first to unsigned long (unnecessarily) and then to unsigned int. Of
> >course, if your system implements a pointer as something bigger than
> >unsigned int (which is what you eventually convert "base" to), then
> >you're screwed anyway and the intermediate typecast to unsigned long
> >doesn't buy you anything at all.
>
> On a 64 bit system, converting pointer to int causes unnecessary
> compiler
> warning, and intermediate long conversion was to avoid that. I will have

Whoa! Hello, hold on, just wait a second there. Do you _really_ want
an unsigned int return out of tbase_get_deferrable() or will an
unsigned long do? If the rest of your code is fine with unsigned long,
then I'd suggest something like:

static inline unsigned long tbase_get_deferrable(tvec_base_t *base)
{
	return ((unsigned long)base & TBASE_DEFERRABLE_FLAG);
}

I don't really know your code (so I could be horribly incorrect here),
but personally I would prefer *heeding* to that warning than _hiding_
it -- it's not unnecessary, it's telling you that you're *losing* data
by converting a pointer (which is always unsigned long) to unsigned
int for 64-bit platforms where sizeof(void *) == sizeof(unsigned long)
== 8 bytes, but sizeof(unsigned int) == 4.

  parent reply	other threads:[~2007-05-10  8:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-08 10:33 Jarek Poplawski
2007-05-08 23:33 ` Andrew Morton
2007-05-09  5:31   ` Jarek Poplawski
2007-05-09 15:59     ` Pallipadi, Venkatesh
2007-05-09 18:29       ` Satyam Sharma
2007-05-09 19:10         ` Pallipadi, Venkatesh
2007-05-10  7:39           ` Jarek Poplawski
2007-05-10  7:57             ` Andrew Morton
2007-05-10  9:29               ` [PATCH] timer: revert " Jarek Poplawski
2007-05-10  9:35                 ` Jarek Poplawski
2007-05-10  8:26           ` Satyam Sharma [this message]
2007-05-10  9:32             ` [PATCH -mm] timer: " Satyam Sharma
2007-05-10  5:52         ` Jarek Poplawski

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=a781481a0705100126x6a649c16ic26409b4ffe80ed3@mail.gmail.com \
    --to=satyam.sharma@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=jarkao2@o2.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg@tv-sign.ru \
    --cc=venkatesh.pallipadi@intel.com \
    /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®