public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/64024] [5 Regression] gcc.dg/vect/vect-simd-clone-6.c ICEs
Date: Mon, 24 Nov 2014 16:06:00 -0000	[thread overview]
Message-ID: <bug-64024-4-5dVGNyTejt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64024-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
Generally calling SCEV analysis again during the transform phase asks for
trouble
(though it may work in most cases).  This means that the simple_iv calls (which
are mostly useless as computed stuff isn't actually used in most cases) should
be avoided at transform time.

Didn't look into this specific case but can do so (just assign the bug to me
then).


  parent reply	other threads:[~2014-11-24 16:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-22 11:58 [Bug tree-optimization/64024] New: " ubizjak at gmail dot com
2014-11-22 17:36 ` [Bug tree-optimization/64024] [5 Regression] " hjl.tools at gmail dot com
2014-11-24 11:26 ` rguenth at gcc dot gnu.org
2014-11-24 15:15 ` jakub at gcc dot gnu.org
2014-11-24 15:56 ` jakub at gcc dot gnu.org
2014-11-24 16:06 ` rguenth at gcc dot gnu.org [this message]
2014-11-24 16:16 ` jakub at gcc dot gnu.org
2014-11-24 16:29 ` rguenth at gcc dot gnu.org
2014-11-24 16:31 ` rguenth at gcc dot gnu.org
2014-11-26 14:54 ` jakub at gcc dot gnu.org
2014-11-27 11:03 ` jakub at gcc dot gnu.org
2014-11-28  9:31 ` jakub at gcc dot gnu.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=bug-64024-4-5dVGNyTejt@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).