mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mirco Tischler <mt-ml@gmx.de>
To: Adrian Bunk <bunk@kernel.org>
Cc: lkml <linux-kernel@vger.kernel.org>, Greg Kroah-Hartman <gregkh@suse.de>
Subject: Re: [BUG: 2.6.26-rc3] ERROR: "____ilog2_NaN" undefined
Date: Mon, 26 May 2008 23:16:46 +0200	[thread overview]
Message-ID: <1211836606.10718.18.camel@mtlp.tischlernetz> (raw)
In-Reply-To: <1211752151.16921.25.camel@mtlp.tischlernetz>

[-- Attachment #1: Type: text/plain, Size: 775 bytes --]

Ok. Situation has changed. I discovered I'm still more dumb than I
thought I am;). There was that link /usr/local/bin/gcc to the gcc-4.4pre
executable that I didn't thought of. the ver_linux script didn't check
that too. So the error only occurs with gcc-4.4. But my version is some
weeks old so I'm currently compiling a fresh svn version to check if the
error still exists.

I also found the config option that causes the error: enabling
OPTIMIZE_FOR_SIZE and thus setting -Os instead of -O2 makes the error go
away, so this is pretty much a compiler problem.
I will check now if the error is still existent in the current developer
version of gcc and then maybe contact the gcc team.

Meanwhile I'm really sorry for the noise and annoyance.

Thanks
Mirco

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-05-26 21:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-25 17:13 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 [this message]
2008-05-27 23:56               ` Adrian Bunk
2008-06-08 12:41                 ` Mirco Tischler
2008-06-09 22:14                   ` Greg KH
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=1211836606.10718.18.camel@mtlp.tischlernetz \
    --to=mt-ml@gmx.de \
    --cc=bunk@kernel.org \
    --cc=gregkh@suse.de \
    --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

all inboxes | Powered by JetHome®