All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Mirco Tischler <mt-ml@gmx.de>
Cc: Adrian Bunk <bunk@kernel.org>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [BUG: 2.6.26-rc3] ERROR: "____ilog2_NaN" undefined
Date: Mon, 9 Jun 2008 15:14:41 -0700	[thread overview]
Message-ID: <20080609221440.GA22227@suse.de> (raw)
In-Reply-To: <20080608144112.1d623ed4@mtlp.tischlernetz>

On Sun, Jun 08, 2008 at 02:41:12PM +0200, Mirco Tischler wrote:
> Here's an update:
> I've contacted the gcc folks. Here is the bugzilla entry:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36359
> We were able to trace the error down to usb_submit_urb() in
> drivers/usb/core/urb.c which calls ilog2() and the gcc falsely assumes its
> argument (urb->interval) to be zero. But as I understood they say it's the
> kernel's fault because the code depends on correct optimization what seems a
> little weird for me as incorrect optimization is a gcc bug IMHO. But I am not
> an expert and maybe I've just understood something wrong because I'm not a
> native speaker.

I'm confused how the kernel code could be at fault here.

How could it be fixed to not be at fault?

thanks,

greg k-h

  reply	other threads:[~2008-06-09 22:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-25 17:13 [BUG: 2.6.26-rc3] ERROR: "____ilog2_NaN" undefined Mirco Tischler
2008-05-25 18:11 ` Adrian Bunk
2008-05-25 19:03   ` Mirco Tischler
2008-05-25 20:18     ` Adrian Bunk
2008-05-25 20:57       ` Mirco Tischler
2008-05-25 21:03         ` Adrian Bunk
2008-05-25 21:49           ` Mirco Tischler
2008-05-26 21:16             ` Mirco Tischler
2008-05-27 23:56               ` Adrian Bunk
2008-06-08 12:41                 ` Mirco Tischler
2008-06-09 22:14                   ` Greg KH [this message]
2008-06-10 10:15                     ` Adrian Bunk

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=20080609221440.GA22227@suse.de \
    --to=gregkh@suse.de \
    --cc=bunk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mt-ml@gmx.de \
    /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.