public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rakdver at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/26449] [4.2 Regression] ICE with -march=pentium4 -ftree-vectorize in matmul_i4.c in loop invariant motion
Date: Thu, 08 Jun 2006 08:20:00 -0000	[thread overview]
Message-ID: <20060608081714.9723.qmail@sourceware.org> (raw)
In-Reply-To: <bug-26449-11811@http.gcc.gnu.org/bugzilla/>



------- Comment #8 from rakdver at gcc dot gnu dot org  2006-06-08 08:17 -------
Subject: Bug 26449

Author: rakdver
Date: Thu Jun  8 08:17:05 2006
New Revision: 114481

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=114481
Log:
        PR rtl-optimization/26449
        * loop-invariant.c (move_invariant_reg): Fail if force_operand fails.

        * gcc.dg/pr26449.c: New test.


Added:
    trunk/gcc/testsuite/gcc.dg/pr26449.c
Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/loop-invariant.c
    trunk/gcc/testsuite/ChangeLog


-- 


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


  parent reply	other threads:[~2006-06-08  8:17 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-23 18:31 [Bug c/26449] New: ICE with -march=pentium4 in matmul_i4.c aldot at gcc dot gnu dot org
2006-02-24 10:26 ` [Bug c/26449] ICE with -march=pentium4 -ftree-vectorize in matmul_i4.c in loop invaraint motion rguenth at gcc dot gnu dot org
2006-02-24 10:46 ` [Bug rtl-optimization/26449] " rguenth at gcc dot gnu dot org
2006-02-24 10:51 ` steven at gcc dot gnu dot org
2006-02-24 18:14 ` [Bug rtl-optimization/26449] [4.2 Regression] ICE with -march=pentium4 -ftree-vectorize in matmul_i4.c in loop invariant motion pinskia at gcc dot gnu dot org
2006-02-24 20:49 ` steven at gcc dot gnu dot org
2006-02-24 20:51 ` pinskia at gcc dot gnu dot org
2006-02-24 21:22 ` rakdver at atrey dot karlin dot mff dot cuni dot cz
2006-05-21 20:54 ` pinskia at gcc dot gnu dot org
2006-06-04 17:50 ` mmitchel at gcc dot gnu dot org
2006-06-04 18:00 ` steven at gcc dot gnu dot org
2006-06-06 10:11 ` rakdver at gcc dot gnu dot org
2006-06-06 18:03 ` rakdver at gcc dot gnu dot org
2006-06-08  8:20 ` rakdver at gcc dot gnu dot org [this message]
2006-06-08 15:36 ` pinskia at gcc dot gnu dot org
2007-06-01  6:39 ` [Bug rtl-optimization/26449] [4.2/4.3 Regression] ICE " ubizjak at gmail dot com
2007-06-01  6:42 ` ubizjak at gmail dot com
2007-06-01  6:42 ` ubizjak at gmail dot com
2007-06-01  7:30 ` ubizjak at gmail dot com
2007-09-08 11:33 ` uros at gcc dot gnu dot org
2007-09-08 11:35 ` ubizjak at gmail dot com
2007-09-08 11:48 ` uros at gcc dot gnu dot org
2007-09-08 11:51 ` ubizjak at gmail dot com
2007-09-14  5:42 ` ubizjak at gmail dot com
2007-09-14  5:49 ` ubizjak at gmail dot com
2007-09-14 15:57 ` rakdver at gcc dot gnu dot org
2007-09-17 15:39 ` rakdver at gcc dot gnu dot org
2007-09-17 16:44 ` [Bug rtl-optimization/26449] [4.2 " ubizjak at gmail dot com
2008-01-13 16:14 ` rguenth at gcc dot gnu dot org
2008-01-15  8:30 ` ubizjak at gmail dot com
2008-04-25  6:28 ` ubizjak at gmail dot com
2008-04-25  6:29 ` ubizjak at gmail dot com
2008-07-04 16:41 ` jsm28 at gcc dot gnu dot org
2009-03-30 15:50 ` jsm28 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=20060608081714.9723.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).