mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Harvey Harrison <harvey.harrison@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>,
	Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] bitops: simplify generic bit finding functions
Date: Sun, 27 Apr 2008 13:38:34 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.1.10.0804271335330.3119@woody.linux-foundation.org> (raw)
In-Reply-To: <1209328161.14173.77.camel@brick>



On Sun, 27 Apr 2008, Harvey Harrison wrote:
>
> Oh, I didn't realize, I only did this because sparse started spewing out
> lots of:
> include/linux/bitops.h:166:32: warning: shift too big (65536) for type unsigned long

Well, that's really just a sparse bug/misfeature that didn't matter 
before.

It happens because the warning is done as part of constant expression 
evaluation, but then the expression isn't actually *used*, so when we 
optimize it away - at a later date - it's too late to undo the warning.

I don't rightly know how to fix it. We do want to do the constant 
evaluation early (since all the optimizations that may then make it a 
non-issue depends on constants being constants!), but in order to not 
output the warning we'd have to turn the constant into a "constant with 
warning 'xyz' if used".

Which we have no support for in sparse yet.

		Linus

  parent reply	other threads:[~2008-04-27 20:39 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-27 20:19 Harvey Harrison
2008-04-27 20:26 ` Linus Torvalds
2008-04-27 20:29   ` Harvey Harrison
2008-04-27 20:36     ` Al Viro
2008-04-27 20:38       ` Harvey Harrison
2008-04-27 20:38     ` Linus Torvalds [this message]
2008-04-27 21:02       ` Al Viro
2008-04-28 14:04   ` Thomas Gleixner
2008-04-28 15:10     ` Alexander van Heukelum
2008-04-28 15:58       ` Thomas Gleixner
2008-04-28 16:25     ` Linus Torvalds
2008-04-28 16:47       ` Thomas Gleixner
2008-04-28 16:54         ` Linus Torvalds
2008-04-28 19:26           ` Thomas Gleixner
2008-04-28 19:37             ` Linus Torvalds
2008-04-28 21:55               ` Ingo Molnar
2008-04-29 10:01               ` [PATCH] bitops: remove "optimizations" Thomas Gleixner
2008-04-29 10:03                 ` David Miller
2008-04-29 12:34                   ` David Miller
2008-04-29 14:20                     ` Ingo Molnar
2008-04-29 22:31                       ` David Miller
2008-04-29 16:51                     ` Thomas Gleixner
2008-04-29 22:58                       ` David Miller
2008-04-29 23:30                         ` David Miller
2008-04-28 19:57           ` [PATCH] bitops: simplify generic bit finding functions Andi Kleen
2008-04-28 14:58   ` Alexander van Heukelum
2008-04-28 14:32 ` Alexander van Heukelum

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=alpine.LFD.1.10.0804271335330.3119@woody.linux-foundation.org \
    --to=torvalds@linux-foundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=harvey.harrison@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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®