public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Janis Johnson <janis187@us.ibm.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/8994: [3.2/3.3 regression] ICE with -O -march=pentium4
Date: Wed, 18 Dec 2002 16:36:00 -0000	[thread overview]
Message-ID: <20021219003601.16802.qmail@sources.redhat.com> (raw)

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

From: Janis Johnson <janis187@us.ibm.com>
To: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, towa8667@student.uu.se,
   gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org
Cc:  
Subject: Re: optimization/8994: [3.2/3.3 regression] ICE with -O -march=pentium4
Date: Wed, 18 Dec 2002 16:29:57 -0800

 The regression reported in PR optimization/8994 showed up
 starting with this patch:
 
 Thu Dec 13 12:31:07 CET 2001  Jan Hubicka  <jh@suse.cz>
 
         * i386.c (override_options): Recognize various CPU variants and
 set
         SSE/MMX/3dNOW flags accordingly.
         * i386.h (MASK_MMX_SET, MASK_SSE_SET, MASK_SSE2_SET,
 MASK_3DNOW_SET,
         MASK_3DNOW_A_SET): New.
         (MASK_ACCUMULATE_OUTGOING_ARGS_SET): New.
         (MASK_NO_ACCUMULATE_OUTGOING_ARGS): Delete.
         (MASK_*): Renumber.
         (TARGET_FLAGS): Use new masks.
         (CPP_CPU_SPECS): Recognize new CPU variants.
         * invoke.texi (-mcpu): Update documentation.
 
 In the ChangeLog and cvs logs, this in included with
 several other files whose changes seem to be separate.
 If I build cc1 just before this patch was added, the test
 compiles cleanly, but when the files i386.c and i386.h are
 updated it gets the same ICE as the mainline.
 
 I used Wolfgang's new test case:
 
 ---------------------
 void foo (double d)
 {
   union { double d; int i; } u;
 
   while (1)
   {
     u.d = d;
     if (u.i & 1) return;
   }
 }
 ---------------------
 
 Here's the compiler output when compiled with
 "-O -march=pentium4" on i686-linux with the mainline
 or the 3.2 branch:
 
 8994.c: In function `foo':
 8994.c:10: error: unable to find a register to spill in class `AREG'
 8994.c:10: error: this is the insn:
 (insn 19 18 20 1 0x2abbc2c0 (set (reg:CCNO 17 flags)
         (compare:CCNO (and:SI (subreg:SI (reg/v:DI 21 rxmm0 [59]) 0)
                 (const_int 1 [0x1]))
             (const_int 0 [0x0]))) 199 {testsi_1} (insn_list 16 (nil))
     (expr_list:REG_DEAD (reg/v:DI 21 rxmm0 [59])
         (nil)))
 8994.c:10: internal compiler error: in spill_failure, at reload1.c:1922
 Please submit a full bug report,
 with preprocessed source if appropriate.
 See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8994
 
 
 


             reply	other threads:[~2002-12-19  0:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-18 16:36 Janis Johnson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-18 13:46 Joseph S. Myers
2002-12-18 13:16 Volker Reichelt
2002-12-18 13:16 Wolfgang Bangerth
2002-12-18 13:06 Joseph S. Myers
2002-12-18 12:56 Wolfgang Bangerth
2002-12-18 12:46 Torbjorn Wassberg
2002-12-18 12:23 bangerth

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=20021219003601.16802.qmail@sources.redhat.com \
    --to=janis187@us.ibm.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).