public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "uweigand at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug regression/53729] [4.8 regression] PR53636 fix caused bb-slp-16.c to FAIL on sparc64 and powerpc64
Date: Tue, 26 Jun 2012 09:06:00 -0000	[thread overview]
Message-ID: <bug-53729-4-pGuENfNo7v@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53729-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Ulrich Weigand <uweigand at gcc dot gnu.org> 2012-06-26 09:05:55 UTC ---
Author: uweigand
Date: Tue Jun 26 09:05:48 2012
New Revision: 188979

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=188979
Log:
    PR tree-optimization/53729
    PR tree-optimization/53636
    * tree-vect-slp.c (vect_slp_analyze_bb_1): Delay call to
    vect_verify_datarefs_alignment until after statements have
    been marked as relevant/irrelevant.
    * tree-vect-data-refs.c (vect_verify_datarefs_alignment):
    Skip irrelevant statements.
    (vect_enhance_data_refs_alignment): Use STMT_VINFO_RELEVANT_P
    instead of STMT_VINFO_RELEVANT.
    (vect_get_data_access_cost): Do not check for supportable
    alignment before calling vect_get_load_cost/vect_get_store_cost.
    * tree-vect-stmts.c (vect_get_store_cost): Do not abort when
    handling unsupported alignment.
    (vect_get_load_cost): Likewise.

Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/tree-vect-data-refs.c
    trunk/gcc/tree-vect-slp.c
    trunk/gcc/tree-vect-stmts.c


  parent reply	other threads:[~2012-06-26  9:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-20 11:26 [Bug regression/53729] New: " mikpe at it dot uu.se
2012-06-20 11:33 ` [Bug regression/53729] " rguenth at gcc dot gnu.org
2012-06-20 15:22 ` uweigand at gcc dot gnu.org
2012-06-26  9:06 ` uweigand at gcc dot gnu.org [this message]
2012-06-26  9:09 ` uweigand 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-53729-4-pGuENfNo7v@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).