From: David Edelsohn <dje@watson.ibm.com>
To: Randy Gobbel <gobbel@andrew.cmu.edu>
Cc: kbhend@business.wm.edu, gdt@linuxppc.org, sbb@gnu.org,
linuxppc-dev@lists.linuxppc.org, egcs@egcs.cygnus.com
Subject: Re: Problem with egcs and denormalized constants?
Date: Thu, 04 Mar 1999 15:52:00 -0000 [thread overview]
Message-ID: <9903042352.AA37658@marc.watson.ibm.com> (raw)
In-Reply-To: Message from Randy Gobbel <gobbel@andrew.cmu.edu> of "Thu, 04 Mar 1999 17:29:52 EST." <36DF0960.404624C0@andrew.cmu.edu>
>>>>> Randy Gobbel writes:
Randy> P.S.: I just said the flMin problem was an egcs bug. It's actually an
Randy> asm bug, because the constant is correct in the .s file:
Randy> .LC8:
Randy> .float 0d1.40129846432481707092e-45
If I understand correctly, the bug actually is in glibc. I
presume that the GNU assembler is not receiving the correct value when it
calls upon glibc to parse the constant for it to emit into the object
file.
David
WARNING: multiple messages have this Message-ID
From: David Edelsohn <dje@watson.ibm.com>
To: Randy Gobbel <gobbel@andrew.cmu.edu>
Cc: kbhend@business.wm.edu, gdt@linuxppc.org, sbb@gnu.org,
linuxppc-dev@lists.linuxppc.org, egcs@egcs.cygnus.com
Subject: Re: Problem with egcs and denormalized constants?
Date: Wed, 31 Mar 1999 23:46:00 -0000 [thread overview]
Message-ID: <9903042352.AA37658@marc.watson.ibm.com> (raw)
Message-ID: <19990331234600.89zruES7NolWiETxsPUL-9zMVfxu_jiGtOWn_VMIR-w@z> (raw)
In-Reply-To: <36DF0960.404624C0@andrew.cmu.edu>
>>>>> Randy Gobbel writes:
Randy> P.S.: I just said the flMin problem was an egcs bug. It's actually an
Randy> asm bug, because the constant is correct in the .s file:
Randy> .LC8:
Randy> .float 0d1.40129846432481707092e-45
If I understand correctly, the bug actually is in glibc. I
presume that the GNU assembler is not receiving the correct value when it
calls upon glibc to parse the constant for it to emit into the object
file.
David
next parent reply other threads:[~1999-03-04 15:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <36DF0960.404624C0@andrew.cmu.edu>
1999-03-04 15:52 ` David Edelsohn [this message]
1999-03-31 23:46 ` David Edelsohn
[not found] <36DF4486.6E098903@andrew.cmu.edu>
1999-03-04 20:02 ` David Edelsohn
[not found] ` < 9903050401.AA41152@marc.watson.ibm.com >
1999-03-05 2:06 ` Gary Thomas
1999-03-31 23:46 ` Gary Thomas
1999-03-31 23:46 ` David Edelsohn
1999-03-04 23:42 ` Gary Thomas
1999-03-31 23:46 ` Gary Thomas
1999-03-04 9:01 Kevin B. Hendricks
1999-03-04 10:57 ` Jerry Quinn
1999-03-31 23:46 ` Jerry Quinn
[not found] ` < 36DEBCB0.7A98EB80@business.wm.edu >
1999-03-05 23:20 ` Gary Thomas
[not found] ` < XFMail.990306072117.gdt@linuxppc.org >
1999-03-06 9:26 ` David Edelsohn
[not found] ` < 9903061726.AA30084@marc.watson.ibm.com >
1999-03-06 22:55 ` Gary Thomas
1999-03-31 23:46 ` Gary Thomas
1999-03-31 23:46 ` David Edelsohn
1999-03-31 23:46 ` Gary Thomas
1999-03-31 23:46 ` Kevin B. Hendricks
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=9903042352.AA37658@marc.watson.ibm.com \
--to=dje@watson.ibm.com \
--cc=egcs@egcs.cygnus.com \
--cc=gdt@linuxppc.org \
--cc=gobbel@andrew.cmu.edu \
--cc=kbhend@business.wm.edu \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=sbb@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).