public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/51581] Integer division by constant is not vectorized
Date: Fri, 15 Jun 2012 11:08:00 -0000	[thread overview]
Message-ID: <bug-51581-4-brD1sIbDiP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51581-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-06-15 11:07:54 UTC ---
Author: jakub
Date: Fri Jun 15 11:07:47 2012
New Revision: 188656

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=188656
Log:
    PR tree-optimization/51581
    * expr.h (choose_multiplier): New prototype.
    * expmed.c (choose_multiplier): No longer static.
    Change multiplier_ptr from rtx * to UHWI *.
    (expand_divmod): Adjust callers.
    * tree-vect-patterns.c (vect_recog_sdivmod_pow2_pattern):
    Renamed to...
    (vect_recog_divmod_pattern): ... this.  Pass bb_vinfo as last
    argument to new_stmt_vec_info.  Attempt to optimize also divisions
    by non-pow2 constants if integer vector division isn't supported.
    * tree-vect-stmts.c (vect_analyze_stmt): If node != NULL,
    don't look at pattern stmts and sequences.

    * gcc.c-torture/execute/pr51581-1.c: New test.
    * gcc.c-torture/execute/pr51581-2.c: New test.
    * gcc.dg/vect/pr51581-1.c: New test.
    * gcc.dg/vect/pr51581-2.c: New test.
    * gcc.dg/vect/pr51581-3.c: New test.
    * gcc.target/i386/avx-pr51581-1.c: New test.
    * gcc.target/i386/avx-pr51581-2.c: New test.
    * gcc.target/i386/avx2-pr51581-1.c: New test.
    * gcc.target/i386/avx2-pr51581-2.c: New test.
    * gcc.dg/vect/slp-26.c (main1): Divide by 0x8031 instead of 3.

Added:
    trunk/gcc/testsuite/gcc.c-torture/execute/pr51581-1.c
    trunk/gcc/testsuite/gcc.c-torture/execute/pr51581-2.c
    trunk/gcc/testsuite/gcc.dg/vect/pr51581-1.c
    trunk/gcc/testsuite/gcc.dg/vect/pr51581-2.c
    trunk/gcc/testsuite/gcc.dg/vect/pr51581-3.c
    trunk/gcc/testsuite/gcc.target/i386/avx-pr51581-1.c
    trunk/gcc/testsuite/gcc.target/i386/avx-pr51581-2.c
    trunk/gcc/testsuite/gcc.target/i386/avx2-pr51581-1.c
    trunk/gcc/testsuite/gcc.target/i386/avx2-pr51581-2.c
Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/expmed.c
    trunk/gcc/expr.h
    trunk/gcc/testsuite/ChangeLog
    trunk/gcc/testsuite/gcc.dg/vect/slp-26.c
    trunk/gcc/tree-vect-patterns.c
    trunk/gcc/tree-vect-stmts.c


  parent reply	other threads:[~2012-06-15 11:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-16 16:25 [Bug tree-optimization/51581] New: " jakub at gcc dot gnu.org
2011-12-16 16:31 ` [Bug tree-optimization/51581] " jakub at gcc dot gnu.org
2011-12-19  9:35 ` rguenth at gcc dot gnu.org
2012-06-13 19:22 ` jakub at gcc dot gnu.org
2012-06-14 13:32 ` jakub at gcc dot gnu.org
2012-06-15 11:08 ` jakub at gcc dot gnu.org [this message]
2012-06-15 11:09 ` jakub at gcc dot gnu.org
2012-06-28 17:54 ` 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-51581-4-brD1sIbDiP@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).