From: Richard Guenther <richard.guenther@gmail.com>
To: Xinliang David Li <davidxl@google.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>, "H.J. Lu" <hjl.tools@gmail.com>
Subject: Re: -fdump-passes -fenable-xxx=func_name_list
Date: Fri, 10 Jun 2011 09:10:00 -0000 [thread overview]
Message-ID: <BANLkTin_J=KbqttEisRoAksoyTqdU7j4SQ@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=ApS2+Qx8QnVmYjadvFbE58_5gJ9qWsjL3Vv6R6BU97w@mail.gmail.com>
On Fri, Jun 10, 2011 at 12:51 AM, Xinliang David Li <davidxl@google.com> wrote:
> Patch is temporally rolled back.
>
> Richard, looks like deeper pass manager cleanup is needed -- I would
> like to delay that. For now, this leaves us two choices -- 1) do cfunc
> push/pop, or 2) do pass dump while executing. None of them is ideal,
> but safe enough.
Well. It seems we should take a step back and look at the whole picture
and try to figure out how it should look like in the end (maybe do that
in London).
For now I prefer 1) over 2).
Thanks,
Richard.
> Thanks,
>
> David
>
> On Thu, Jun 9, 2011 at 3:32 PM, Xinliang David Li <davidxl@google.com> wrote:
>> Though I can not reproduce it, it might be related to what Richard
>> mentioned in the review -- The TODO's are executed though the pass is
>> not. This opened up a can of worm -- I will revert the patches for
>> now.
>>
>> David
>>
>>
>> On Thu, Jun 9, 2011 at 3:05 PM, H.J. Lu <hjl.tools@gmail.com> wrote:
>>> On Tue, Jun 7, 2011 at 11:54 AM, Xinliang David Li <davidxl@google.com> wrote:
>>>> Please review the attached two patches.
>>>>
>>>> In the first patch, gate functions are cleaned up. All the per
>>>> function legality checks are moved into the executor and the
>>>> optimization heuristic checks (optimize for size) remain in the
>>>> gators. These allow the the following overriding order:
>>>>
>>>> common flags (O2, -ftree-vrp, -fgcse etc) <--- compiler
>>>> heuristic (optimize for size/speed) <--- -fdisable/enable forcing pass
>>>> options <--- legality check
>>>>
>>>> Testing under going. Ok for trunk?
>>>>
>>>
>>> This caused:
>>>
>>> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49350
>>>
>>> --
>>> H.J.
>>>
>>
>
next prev parent reply other threads:[~2011-06-10 9:04 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BANLkTikXRUTmZZokg4OtJA5fBrWUG+7yZux3=CLDBox1Q+Qhtw@mail.gmail.com>
2011-06-01 8:51 ` Richard Guenther
2011-06-01 16:17 ` Xinliang David Li
2011-06-01 17:24 ` Xinliang David Li
2011-06-05 17:25 ` Xinliang David Li
2011-06-06 11:22 ` Richard Guenther
2011-06-06 15:54 ` Xinliang David Li
2011-06-06 15:59 ` Richard Guenther
2011-06-06 19:21 ` Xinliang David Li
2011-06-07 10:11 ` Richard Guenther
2011-06-01 19:29 ` Richard Guenther
2011-06-01 19:46 ` Xinliang David Li
2011-06-02 7:13 ` Xinliang David Li
2011-06-05 17:25 ` Xinliang David Li
2011-06-06 11:38 ` Richard Guenther
2011-06-06 16:00 ` Xinliang David Li
2011-06-06 19:23 ` Xinliang David Li
2011-06-07 10:10 ` Richard Guenther
2011-06-07 16:24 ` Xinliang David Li
2011-06-07 19:09 ` Xinliang David Li
2011-06-07 20:39 ` Xinliang David Li
2011-06-08 9:06 ` Richard Guenther
2011-06-08 8:54 ` Richard Guenther
2011-06-09 22:16 ` H.J. Lu
2011-06-09 22:24 ` Carrot Wei
2011-06-09 22:32 ` Xinliang David Li
2011-06-09 22:51 ` Xinliang David Li
2011-06-09 23:28 ` Xinliang David Li
2011-06-10 9:10 ` Richard Guenther [this message]
2011-06-10 16:37 ` Xinliang David Li
2011-06-01 19:29 ` Xinliang David Li
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='BANLkTin_J=KbqttEisRoAksoyTqdU7j4SQ@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=davidxl@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
/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).