From: Ulrich Drepper <drepper@cygnus.com>
To: egcs@cygnus.com
Subject: internal error asm
Date: Mon, 23 Feb 1998 15:08:00 -0000 [thread overview]
Message-ID: <r2iuq6ggb9.fsf@happy.cygnus.com> (raw)
Hi,
the following little piece of code crashed all gcc versions on ix86
which I could test:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
#include <stdio.h>
extern double bar (double);
int
baz (double d)
{
double e = bar (d);
#ifdef BROKEN
asm volatile ("" : : : "st");
#else
asm volatile ("" : : : "memory");
#endif
return printf ("%lg\n", e);
}
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
drepper@happy drepper$ gcc -Wa,-al -c v.c -O3 -DBROKEN
gcc: Internal compiler error: program cc1 got fatal signal 11
Not defining BROKEN lets the compiler finish but the result is not the
same (I want to force `e' being written to memory before calling
printf). It's necessary to compile libm correctly.
-- Uli
---------------. drepper at gnu.org ,-. 1325 Chesapeake Terrace
Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
Cygnus Solutions `--' drepper at cygnus.com `------------------------
next reply other threads:[~1998-02-23 15:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-23 15:08 Ulrich Drepper [this message]
1998-02-24 5:07 ` Jeffrey A Law
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=r2iuq6ggb9.fsf@happy.cygnus.com \
--to=drepper@cygnus.com \
--cc=egcs@cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).