public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Reichelt <reichelt@igpm.rwth-aachen.de>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/7063: internal compiler error: Internal compiler error in failed_reload, at reload1.c:5047
Date: Thu, 27 Jun 2002 05:46:00 -0000	[thread overview]
Message-ID: <20020627120602.10311.qmail@sources.redhat.com> (raw)

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

From: Reichelt <reichelt@igpm.rwth-aachen.de>
To: gcc-gnats@gcc.gnu.org, spigel@olvs.miee.ru, gcc-bugs@gcc.gnu.org,
        nobody@gcc.gnu.org
Cc:  
Subject: Re: optimization/7063: internal compiler error: Internal compiler error in failed_reload, at reload1.c:5047
Date: Thu, 27 Jun 2002 14:35:10 +0200

 Hi,
 
 the bug can reproduced with the following code snippet:
 
 ------------------------snip here----------------------
 void foo()
 {
    char                      (*c)[2];
    float                     *fp;
    int                       i, j;
    union { float r; int i; } u;
 
    for ( i=0; i<j; ++i )
       if (j==1)
       {
          ++fp;
          u.r = *fp; c[i][0] = u.i>0 ? 0 : (u.r+=1, u.i);
          u.r = *fp; c[i][0] = u.i>0 ? 0 : (u.r+=1, u.i);
       }
 }
 ------------------------snip here----------------------
 
 Just compile it with "gcc -march=athlon -O2 -fforce-addr -c" to get
 the following error message:
 
 bug.c: In function `foo':
 bug.c:15: could not find a spill register
 (insn 50 48 51 (set (subreg:SF (reg:QI 67) 0)
         (plus:SF (subreg:SF (reg/v:SI 0 eax [62]) 0)
             (reg:SF 8 st(0) [69]))) 525 {*fop_sf_comm_nosse} (nil)
     (expr_list:REG_DEAD (reg/v:SI 0 eax [62])
         (nil)))
 bug.c:15: Internal compiler error in failed_reload, at reload1.c:5050
 Please submit a full bug report, [etc.]
 
 The bug is in gcc 3.1, recent snapshots of 3.1.1 and the main trunk.
 It's a regression from gcc 3.0.x.
 
 By the way, in the tar archive that was attached to the bug report
 there was another file (psout.i) that causes an athlon-related ICE.
 I opened another PR for that one (PR 7134).
 
 Greetings,
 Volker Reichelt
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7063
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7134
 
 


             reply	other threads:[~2002-06-27 12:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-27  5:46 Reichelt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-07-02 13:49 gerald
2002-07-01  4:46 Sergei Pachkov
2002-07-01  1:53 gerald
2002-06-18  5:23 spigel

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=20020627120602.10311.qmail@sources.redhat.com \
    --to=reichelt@igpm.rwth-aachen.de \
    --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).