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/53773] Vectorizer generates non-canonical multiplies
Date: Mon, 30 Jul 2012 08:47:00 -0000 [thread overview]
Message-ID: <bug-53773-4-Kff0jZnGTN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53773-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53773
--- Comment #6 from rguenther at suse dot de <rguenther at suse dot de> 2012-07-30 08:47:35 UTC ---
On Sun, 29 Jul 2012, wschmidt at gcc dot gnu.org wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53773
>
> William J. Schmidt <wschmidt at gcc dot gnu.org> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> AssignedTo|unassigned at gcc dot |wschmidt at gcc dot gnu.org
> |gnu.org |
> Target Milestone|--- |4.8.0
>
> --- Comment #5 from William J. Schmidt <wschmidt at gcc dot gnu.org> 2012-07-29 16:54:45 UTC ---
> I'll take this one.
>
> I think the assumption of operand placement is too embedded to tease out
> easily, so I'm going to approach this by re-canonicalizing PLUS_EXPR,
> POINTER_PLUS_EXPR, and MULT_EXPR when operand swapping has occurred. Are there
> other tree codes that could be broken?
I don't think so
next prev parent reply other threads:[~2012-07-30 8:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-25 22:16 [Bug tree-optimization/53773] New: " wschmidt at gcc dot gnu.org
2012-06-26 8:31 ` [Bug tree-optimization/53773] " jakub at gcc dot gnu.org
2012-06-26 8:36 ` rguenther at suse dot de
2012-06-26 8:52 ` rguenth at gcc dot gnu.org
2012-07-27 16:27 ` wschmidt at gcc dot gnu.org
2012-07-29 16:55 ` wschmidt at gcc dot gnu.org
2012-07-29 16:56 ` wschmidt at gcc dot gnu.org
2012-07-30 8:47 ` rguenther at suse dot de [this message]
2012-07-31 12:25 ` wschmidt at gcc dot gnu.org
2012-07-31 12:26 ` wschmidt 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-53773-4-Kff0jZnGTN@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).