public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Joe Buck <Joe.Buck@synopsys.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/8098: gcc is crashing
Date: Fri, 11 Oct 2002 09:56:00 -0000	[thread overview]
Message-ID: <20021011165601.7464.qmail@sources.redhat.com> (raw)

The following reply was made to PR c/8098; it has been noted by GNATS.

From: Joe Buck <Joe.Buck@synopsys.com>
To: ebotcazou@libertysurf.fr (Eric Botcazou)
Cc: Joe.Buck@synopsys.COM,
	gdr@integrable-solutions.net (Gabriel Dos Reis),
	fojtik@vision.felk.cvut.cz, gcc-bugs@gcc.gnu.org,
	gcc-gnats@gcc.gnu.org
Subject: Re: c/8098: gcc is crashing
Date: Fri, 11 Oct 2002 09:50:16 -0700 (PDT)

 > > Hmm, this used to be a sign of an ICE being disabled; I didn't run the
 > > actual code so my comment may be moot.
 > 
 > Looks like it isn't:
 > 
 > gcc -Wall -mcpu=i386 -c libm.i
 > libm.c: In function `fmodf':
 > libm.c:727: error: output constraint 0 cannot be specified together with "st" clobber
 > libm.c:729: internal compiler error: in convert_regs_1, at reg-stack.c:2734
 > Please submit a full bug report,
 > with preprocessed source if appropriate.
 > See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
 > 
 > gcc version 3.3 20021007 (experimental)
 
 I tested against the 3.2 branch, not the trunk (3.3).  There is no crash
 in 
 
 gcc version 3.2.1 20021007 (prerelease
 
 
 


             reply	other threads:[~2002-10-11 16:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-11  9:56 Joe Buck [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-11  3:06 Eric Botcazou
2002-10-10 17:16 Gabriel Dos Reis
2002-10-10 17:07 jbuck

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=20021011165601.7464.qmail@sources.redhat.com \
    --to=joe.buck@synopsys.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.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).