public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/30930] [4.3 Regression] vector can cause to create an extra variable, DECL_GIMPLE_REG_P not recomputed
Date: Fri, 19 Sep 2008 22:25:00 -0000	[thread overview]
Message-ID: <20080919222421.12446.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30930-6528@http.gcc.gnu.org/bugzilla/>



------- Comment #13 from pinskia at gcc dot gnu dot org  2008-09-19 22:24 -------
Fixed on the trunk.


-- 

pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
      Known to work|4.2.3                       |4.2.3 4.4.0
            Summary|[4.3/4.4 Regression] vector |[4.3 Regression] vector can
                   |can cause to create an extra|cause to create an extra
                   |variable, DECL_GIMPLE_REG_P |variable, DECL_GIMPLE_REG_P
                   |not recomputed              |not recomputed


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


  parent reply	other threads:[~2008-09-19 22:25 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-22 21:53 [Bug tree-optimization/30930] New: [4.3 Regression] vector can cause to create an extra variable pinskia at gcc dot gnu dot org
2007-02-22 23:12 ` [Bug tree-optimization/30930] " pinskia at gcc dot gnu dot org
2007-02-23  9:56 ` rguenth at gcc dot gnu dot org
2007-02-23 22:48 ` pinskia at gcc dot gnu dot org
2007-06-29 17:58 ` mmitchel at gcc dot gnu dot org
2008-01-13 14:56 ` [Bug tree-optimization/30930] [4.3 Regression] vector can cause to create an extra variable, DECL_GIMPLE_REG_P not recomputed rguenth at gcc dot gnu dot org
2008-01-13 18:17 ` pinskia at gcc dot gnu dot org
2008-03-15  0:44 ` [Bug tree-optimization/30930] [4.3/4.4 " jsm28 at gcc dot gnu dot org
2008-06-06 14:58 ` rguenth at gcc dot gnu dot org
2008-08-27 22:03 ` jsm28 at gcc dot gnu dot org
2008-09-17 22:29 ` pinskia at gcc dot gnu dot org
2008-09-17 22:42 ` pinskia at gcc dot gnu dot org
2008-09-17 22:51 ` pinskia at gcc dot gnu dot org
2008-09-18  1:01 ` pinskia at gcc dot gnu dot org
2008-09-18  8:24 ` rguenther at suse dot de
2008-09-19 22:25 ` pinskia at gcc dot gnu dot org [this message]
2008-09-19 22:26 ` [Bug tree-optimization/30930] [4.3 " pinskia at gcc dot gnu dot org
2009-01-24 10:40 ` rguenth at gcc dot gnu dot org
2009-04-16 15:42 ` pinskia at gcc dot gnu dot org
2009-04-22 15:13 ` rguenth at gcc dot gnu dot org
2009-08-04 12:35 ` rguenth at gcc dot gnu dot org
2010-04-20 13:27 ` rguenth 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=20080919222421.12446.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).