public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ienkovich at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/64434] [5 Regression] Performance regression after operand canonicalization (r216728).
Date: Thu, 15 Jan 2015 11:39:00 -0000	[thread overview]
Message-ID: <bug-64434-4-LLCOmbcNqI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64434-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #14 from ienkovich at gcc dot gnu.org ---
Author: ienkovich
Date: Thu Jan 15 11:39:20 2015
New Revision: 219646

URL: https://gcc.gnu.org/viewcvs?rev=219646&root=gcc&view=rev
Log:
gcc/

    PR tree-optimization/64434
    * cfgexpand.c (reorder_operands): New function.
    (expand_gimple_basic_block): Insert call of reorder_operands if
    optimized is true.

gcc/testsuite/

    PR tree-optimization/64434
    * gcc.dg/torture/pr64434.c: New test.


Added:
    trunk/gcc/testsuite/gcc.dg/torture/pr64434.c
Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/cfgexpand.c
    trunk/gcc/testsuite/ChangeLog


  parent reply	other threads:[~2015-01-15 11:39 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-29 15:15 [Bug tree-optimization/64434] New: " ysrumyan at gmail dot com
2014-12-29 15:17 ` [Bug tree-optimization/64434] " ysrumyan at gmail dot com
2014-12-29 15:47 ` [Bug tree-optimization/64434] [5 Regression] Performance regression after operand cannibalization (r216728) hjl.tools at gmail dot com
2014-12-29 15:48 ` hjl.tools at gmail dot com
2014-12-29 16:17 ` ysrumyan at gmail dot com
2014-12-29 16:18 ` ysrumyan at gmail dot com
2014-12-29 16:20 ` ysrumyan at gmail dot com
2014-12-29 16:25 ` ysrumyan at gmail dot com
2014-12-29 16:36 ` hjl.tools at gmail dot com
2014-12-29 16:56 ` ysrumyan at gmail dot com
2014-12-29 17:01 ` [Bug tree-optimization/64434] [5 Regression] Performance regression after operand canonicalization (r216728) hjl.tools at gmail dot com
2014-12-29 17:08 ` rguenther at suse dot de
2015-01-13 11:23 ` rguenth at gcc dot gnu.org
2015-01-13 16:04 ` jakub at gcc dot gnu.org
2015-01-14  9:45 ` rguenther at suse dot de
2015-01-15 11:39 ` ienkovich at gcc dot gnu.org [this message]
2015-01-15 11:44 ` rguenth at gcc dot gnu.org
2015-01-15 11:44 ` rguenth at gcc dot gnu.org
2015-01-16 14:23 ` ienkovich at gcc dot gnu.org
2015-02-08  9:34 ` pinskia at gcc dot gnu.org
2015-02-09 10:27 ` ysrumyan at gmail dot com
2015-02-09 10:28 ` ysrumyan at gmail dot com

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-64434-4-LLCOmbcNqI@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).