public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jgreenhalgh at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/66119] [5/6 Regression] in optimization of avx-code
Date: Mon, 22 Jun 2015 12:48:00 -0000	[thread overview]
Message-ID: <bug-66119-4-I268JZ0kdm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66119-4@http.gcc.gnu.org/bugzilla/>

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

James Greenhalgh <jgreenhalgh at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
           Assignee|unassigned at gcc dot gnu.org      |jgreenhalgh at gcc dot gnu.org

--- Comment #10 from James Greenhalgh <jgreenhalgh at gcc dot gnu.org> ---
Yes, sorry for the delay - this completely slipped my mind. I'll start working
on it today.

I think I'm going to go back to the design in some of the earlier proposals for
r217191 and move the call to the hookized MOVE_RATIO in to SRA. It makes the
logic a little messier, as we have to check for parameters, then call off to
the target if they are not set. But that will be the only way we can permit
modifying MOVE_RATIO on a per-function basis. The end result should look
something like
https://gcc.gnu.org/ml/gcc-patches/2014-09/msg02267.html


  parent reply	other threads:[~2015-06-22 12:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-12 10:00 [Bug c++/66119] New: Regression " joachim.schoeberl at tuwien dot ac.at
2015-05-12 10:08 ` [Bug c++/66119] [5/6 Regression] " jakub at gcc dot gnu.org
2015-05-12 10:11 ` rguenth at gcc dot gnu.org
2015-05-12 10:15 ` [Bug tree-optimization/66119] " rguenth at gcc dot gnu.org
2015-05-12 10:16 ` rguenth at gcc dot gnu.org
2015-05-12 10:27 ` rguenth at gcc dot gnu.org
2015-05-12 10:43 ` jgreenhalgh at gcc dot gnu.org
2015-05-13 10:59 ` rguenth at gcc dot gnu.org
2015-06-22 12:11 ` rguenth at gcc dot gnu.org
2015-06-22 12:48 ` jgreenhalgh at gcc dot gnu.org [this message]
2015-07-02 16:27 ` jgreenhalgh at gcc dot gnu.org
2015-07-03  9:15 ` rguenth at gcc dot gnu.org
2015-07-03  9:26 ` jgreenhalgh at gcc dot gnu.org
2015-07-03  9:54 ` jgreenhalgh 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-66119-4-I268JZ0kdm@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).