public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "steven at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug regression/19120] [4.0 Regression] ICE: in ten_to_ptwo, at real.c:2007
Date: Thu, 23 Dec 2004 12:55:00 -0000 [thread overview]
Message-ID: <20041223125529.1124.qmail@sourceware.org> (raw)
In-Reply-To: <20041221215248.19120.v.haisman@sh.cvut.cz>
------- Additional Comments From steven at gcc dot gnu dot org 2004-12-23 12:55 -------
This is not a wrong-code bug, not as far as we can tell right now, at
least. There is way too little information to say anything at all about
this problem. We need your help here ;-)
Do you have a self-contained test case that shows this bug? What is the
exact configure line you used (use 'cat configargs.h' in $build/gcc, the
directory with the failing build)? What version of gcc is this (use
`cat version.c' in $source/gcc, the directory with gcc sources that you
are trying to bootstrap).
See also http://gcc.gnu.org/bugs.html.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Keywords|wrong-code |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19120
next prev parent reply other threads:[~2004-12-23 12:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-21 21:52 [Bug bootstrap/19120] New: " v dot haisman at sh dot cvut dot cz
2004-12-21 21:56 ` [Bug regression/19120] [4.0 Regression] " pinskia at gcc dot gnu dot org
2004-12-23 12:55 ` steven at gcc dot gnu dot org [this message]
2004-12-27 1:07 ` pinskia at gcc dot gnu dot org
2004-12-27 22:44 ` v dot haisman at sh dot cvut dot cz
2004-12-28 0:02 ` v dot haisman at sh dot cvut dot cz
2005-01-28 0:37 ` steven at gcc dot gnu dot org
2005-02-09 14:20 ` steven at gcc dot gnu dot org
2005-02-23 15:20 ` steven at gcc dot gnu dot org
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=20041223125529.1124.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).