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/53645] Missed optimization for vector integer division lowering
Date: Tue, 12 Jun 2012 18:34:00 -0000 [thread overview]
Message-ID: <bug-53645-4-dpKUn74XBG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53645-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53645
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-06-12 18:33:56 UTC ---
I think we've talked about enhancing the pattern recognizer to expand it as
mult at the tree level, reusing parts of the expander code for that. I believe
I've looked at it, but can't find any patch (I think it was around mid December
when
sdivmod pattern recognizer has been added). I'll look at it again.
next prev parent reply other threads:[~2012-06-12 18:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-12 12:45 [Bug c/53645] New: Missed optimization for division of vector types andrii.riabushenko at barclays dot com
2012-06-12 13:34 ` [Bug c/53645] " rguenth at gcc dot gnu.org
2012-06-12 13:37 ` [Bug tree-optimization/53645] Missed optimization for vector integer division lowering rguenth at gcc dot gnu.org
2012-06-12 18:34 ` jakub at gcc dot gnu.org [this message]
2012-06-12 20:55 ` pinskia at gcc dot gnu.org
2012-06-13 9:46 ` rguenth at gcc dot gnu.org
2012-06-27 8:50 ` jakub at gcc dot gnu.org
2012-06-28 11:38 ` jakub at gcc dot gnu.org
2012-06-28 12:34 ` jakub at gcc dot gnu.org
2012-06-28 17:53 ` jakub at gcc dot gnu.org
2012-07-01 10:24 ` ubizjak at gmail dot com
2012-07-02 6:56 ` jakub at gcc dot gnu.org
2012-07-02 7:00 ` 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-53645-4-dpKUn74XBG@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).