public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jingyu at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/42691] [4.4/4.5 regression] problematic REG_EQUAL note added to SUBREG
Date: Fri, 15 Jan 2010 19:09:00 -0000	[thread overview]
Message-ID: <20100115190905.19958.qmail@sourceware.org> (raw)
In-Reply-To: <bug-42691-17567@http.gcc.gnu.org/bugzilla/>



------- Comment #13 from jingyu at gcc dot gnu dot org  2010-01-15 19:09 -------
Subject: Bug 42691

Author: jingyu
Date: Fri Jan 15 19:08:53 2010
New Revision: 155945

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=155945
Log:
Backport from mainline(4.5) to fix a regression bug.

2010-01-15  Jing Yu  <jingyu@google.com>

        PR rtl-optimization/42691
        * combine.c (try_combine): Set changed_i3_dest to 1 when I2 and I3 set
        a pseudo to a constant and are merged, and adjust comments.

2010-01-15  Jing Yu  <jingyu@google.com>

        PR rtl-optimization/42691
        * gcc.c-torture/execute/pr42691.c: New.

Added:
    branches/gcc-4_4-branch/gcc/testsuite/gcc.c-torture/execute/pr42691.c
Modified:
    branches/gcc-4_4-branch/gcc/ChangeLog
    branches/gcc-4_4-branch/gcc/combine.c
    branches/gcc-4_4-branch/gcc/testsuite/ChangeLog


-- 


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


  parent reply	other threads:[~2010-01-15 19:09 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-11 19:45 [Bug middle-end/42691] New: Wrong REG_EQUAL note is added to SUBREG node jingyu at google dot com
2010-01-11 19:59 ` [Bug middle-end/42691] " jingyu at google dot com
2010-01-11 22:00 ` [Bug rtl-optimization/42691] problematic REG_EQUAL note added to SUBREG ebotcazou at gcc dot gnu dot org
2010-01-12  2:45 ` jingyu at google dot com
2010-01-12  8:57 ` ebotcazou at gcc dot gnu dot org
2010-01-12  9:33 ` ramana at gcc dot gnu dot org
2010-01-12 22:22 ` jingyu at google dot com
2010-01-13  1:18 ` jingyu at google dot com
2010-01-13 10:03 ` ebotcazou at gcc dot gnu dot org
2010-01-13 20:04 ` jingyu at google dot com
2010-01-13 22:57 ` jingyu at google dot com
2010-01-13 23:27 ` ebotcazou at gcc dot gnu dot org
2010-01-14  0:13 ` jingyu at google dot com
2010-01-14  9:32 ` [Bug rtl-optimization/42691] [4.4/4.5 regression] " rguenth at gcc dot gnu dot org
2010-01-15 18:48 ` jingyu at gcc dot gnu dot org
2010-01-15 19:09 ` jingyu at gcc dot gnu dot org [this message]
2010-01-15 20:59 ` sezeroz at gmail dot com
2010-01-15 21:11 ` mikpe at it dot uu dot se
2010-01-15 21:14 ` jingyu at google dot com
2010-01-15 21:42 ` mikpe at it dot uu dot se
2010-01-15 21:46 ` jingyu at google dot com
2010-01-15 21:50 ` ebotcazou at gcc dot gnu dot org
2010-01-15 21:54 ` jingyu at gcc dot gnu dot org
2010-01-15 21:59 ` jakub at gcc dot gnu dot org
2010-01-15 22:12 ` jingyu at gcc dot gnu dot org
2010-01-15 22:25 ` jingyu at google dot com
2010-01-16 16:05 ` jakub at gcc dot gnu dot org
2010-01-20 23:30 ` rguenth at gcc dot gnu dot org
2010-01-20 23:48 ` jingyu at google dot com

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