Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "H . J . Lu" <hjl@lucon.org>
To: Hartvig Ekner <hartvige@mips.com>
Cc: user alias <linux-mips@oss.sgi.com>
Subject: Re: Compiler problem in glibc
Date: Sun, 17 Mar 2002 10:41:24 -0800	[thread overview]
Message-ID: <20020317104124.A4002@lucon.org> (raw)
In-Reply-To: <200203171052.g2HAqGb27844@coplin09.mips.com>; from hartvige@mips.com on Sun, Mar 17, 2002 at 11:52:15AM +0100

On Sun, Mar 17, 2002 at 11:52:15AM +0100, Hartvig Ekner wrote:
> I have found a problem in glibc caused by the gcc-2.96-99.1 compiler
> from H.J's miniport.
> 
> in the exp() function (file w_expf.c), there is code like: 
> 
> #ifdef __STDC__
>         float __expf(float x)           /* wrapper expf */
> #else
>         float __expf(x)                 /* wrapper expf */
>         float x;
> #endif
> {
> #ifdef _IEEE_LIBM
>         return __ieee754_expf(x);
> #else
>         float z;
>         z = __ieee754_expf(x);
>         if(_LIB_VERSION == _IEEE_) return z;
> 
>         if(__finitef(x)) {
>             if(x>o_threshold)
> 
> 
> (IEEE_LIBM is not set). Note that there are two function calls (ieee754_expf
> and finitef()) followed by a FP if-statement (x>o_threshold). This 
> translates into:
> 

I believe it has been reported before and is fixed in gcc 3.1 at the
time.


H.J.

  parent reply	other threads:[~2002-03-17 18:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-17 10:52 Compiler problem in glibc Hartvig Ekner
2002-03-17 10:52 ` Hartvig Ekner
2002-03-17 18:41 ` H . J . Lu [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-03-18  0:55 Zhang Fuxin

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=20020317104124.A4002@lucon.org \
    --to=hjl@lucon.org \
    --cc=hartvige@mips.com \
    --cc=linux-mips@oss.sgi.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