From: Zack Weinberg <zack@rabi.columbia.edu>
To: Horst von Brand <vonbrand@sleipnir.valparaiso.cl>
Cc: egcs@cygnus.com, libc-alpha@cygnus.com
Subject: Re: egcs-19981005 on i586-linux-gnu + glibc-2.0.96
Date: Tue, 06 Oct 1998 23:03:00 -0000 [thread overview]
Message-ID: <199810070602.CAA00521@blastula.phys.columbia.edu> (raw)
In-Reply-To: <199810070232.WAA10250@sleipnir.valparaiso.cl>
On Tue, 06 Oct 1998 22:32:54 -0500, Horst von Brand wrote:
>The build of egcs crashes after the third stage, when building libiberty:
>
> /usr/src/build/build-egcs-19981005/gcc/xgcc -B/usr/src/build/build-egcs-1998
>1005/gcc/ -c -DHAVE_CONFIG_H -O2 -fomit-frame-pointer -march=pentium -I. -I../
>../../egcs-19981005/libiberty/../include -fpic ../../../egcs-19981005/libiber
>ty/floatformat.c -o pic/floatformat.o
>/usr/include/bits/mathinline.h: In function `floatformat_to_double':
>/usr/include/bits/mathinline.h:495: `asm' operand requires impossible reload
This is an improvement over previous snapshots, which would silently
generate incorrect code from mathinline.h.
The offending function is:
extern inline double ldexp (double x, int y)
{
register long double v;
asm volatile ("fscale" : "=t" (v) : "0" (x), "u" ((long double) y));
return v;
}
I bet it won't have any trouble compiling this snippet by itself, but will
puke when it's inlined. (Take out "extern inline" to try compiling it by
itself.)
libc people: Anyone know why there are volatile qualifiers on the
mathinline.h asms?
zw
prev parent reply other threads:[~1998-10-06 23:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-10-06 22:02 Horst von Brand
1998-10-06 23:03 ` Zack Weinberg [this message]
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=199810070602.CAA00521@blastula.phys.columbia.edu \
--to=zack@rabi.columbia.edu \
--cc=egcs@cygnus.com \
--cc=libc-alpha@cygnus.com \
--cc=vonbrand@sleipnir.valparaiso.cl \
/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).