public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/65136] [5 Regression] VRP inserts unnecessary constant copy in the loop
Date: Mon, 23 Feb 2015 10:00:00 -0000	[thread overview]
Message-ID: <bug-65136-4-oZ5rfR1NO2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65136-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65136

--- Comment #7 from rguenther at suse dot de <rguenther at suse dot de> ---
On Fri, 20 Feb 2015, ubizjak at gmail dot com wrote:

> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65136
> 
> --- Comment #6 from Uroš Bizjak <ubizjak at gmail dot com> ---
> (In reply to Richard Biener from comment #3)
> > After the patch the assembly difference between 4.9 and 5 is
> 
> Hm, I don't see the difference with -O2, 4.9.3 vs. 5.0:

Must be local patches in my tree then.
>From gcc-bugs-return-478145-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Feb 23 09:51:56 2015
Return-Path: <gcc-bugs-return-478145-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30950 invoked by alias); 23 Feb 2015 09:51:55 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 30897 invoked by uid 48); 23 Feb 2015 09:51:50 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/65148] ICE:  in get_biv_step, at loop-iv.c:823
Date: Mon, 23 Feb 2015 10:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 4.9.2
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-65148-4-t1hX85yz44@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65148-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65148-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-02/txt/msg02477.txt.bz2
Content-length: 179

https://gcc.gnu.org/bugzilla/show_bug.cgi?ide148

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Works for me on x86_64, so probably also latent on trunk?


      parent reply	other threads:[~2015-02-23  9:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-20  9:56 [Bug tree-optimization/65136] New: " izamyatin at gmail dot com
2015-02-20 12:43 ` [Bug tree-optimization/65136] [5 Regression] " rguenth at gcc dot gnu.org
2015-02-20 17:03 ` rguenth at gcc dot gnu.org
2015-02-20 17:05 ` rguenth at gcc dot gnu.org
2015-02-20 18:20 ` ubizjak at gmail dot com
2015-02-23 10:00 ` rguenther at suse dot de [this message]

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=bug-65136-4-oZ5rfR1NO2@http.gcc.gnu.org/bugzilla/ \
    --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).