public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "random at rnd dot cx" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/15068] ICE in elim_reg_cond
Date: Wed, 21 Jul 2004 01:38:00 -0000	[thread overview]
Message-ID: <20040721013812.20967.qmail@sourceware.org> (raw)
In-Reply-To: <20040422102055.15068.pb@gcc.gnu.org>


------- Additional Comments From random at rnd dot cx  2004-07-21 01:38 -------
I have had the same problem with GCC 3.2.3 (as well as 3.3.3 and 3.4.0),
building a native arm compiler.

I don't know anything substantial about GCC internals, so please excuse if this
comment is totally worthless...but:

In a cursory look at elim_reg_cond, it looked to me as though the function was
encountering an unexpected rtx code.  So I checked, and found that when the ICE
is encountered it's because elim_reg_cond is called with an rtx with code 0
(UNKNOWN).

So in an effort to work around the problem, I modified elim_reg_cond so that
instead of calling abort() it simply returns the original rtx, and as far as I
can tell that does seem to work. (At least, when I ran the test suites for the
glibc I built with this workaround, the tests for the relevant functions all
passed.)


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15068


  parent reply	other threads:[~2004-07-21  1:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-22 11:20 [Bug optimization/15068] New: " pb at gcc dot gnu dot org
2004-04-22 11:20 ` [Bug optimization/15068] " pb at gcc dot gnu dot org
2004-05-01  1:04 ` dhazeghi at yahoo dot com
2004-05-17 11:51 ` [Bug rtl-optimization/15068] " rearnsha at gcc dot gnu dot org
2004-07-21  1:38 ` random at rnd dot cx [this message]
2004-07-21 10:20 ` rearnsha at gcc dot gnu dot org
2004-08-02 13:19 ` cvs-commit at gcc dot gnu dot org
2004-08-02 13:57 ` cvs-commit at gcc dot gnu dot org
2004-08-02 16:52 ` pinskia at gcc dot gnu dot org
2005-02-22  4:50 ` pinskia at gcc dot gnu dot org
2005-05-22 18:47 ` pinskia at gcc dot gnu dot org
2005-06-15 14:59 ` xuguangyi at ee dot buaa dot edu dot cn
2005-06-15 15:05 ` rearnsha at gcc dot gnu dot org
     [not found] <bug-15068-592@http.gcc.gnu.org/bugzilla/>
2006-04-02  6:48 ` shap at eros-os dot org
2006-04-02  6:52 ` pinskia at gcc dot gnu dot org
2006-04-02  9:05 ` mikpe at csd dot uu dot se

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=20040721013812.20967.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).