From: "H.J. Lu" <hjl.tools@gmail.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>,
Jeffrey Law <law@redhat.com>,
Michael Meissner <gnu@the-meissners.org>,
Jason Merrill <jason@redhat.com>,
davem@redhat.com, Diego Novillo <dnovillo@google.com>,
Ian Lance Taylor <ian@airs.com>,
Jim Wilson <wilson@tuliptree.org>,
richard.sandiford@linaro.org, rdsandiford@googlemail.com
Subject: Re: PING: PATCH: PR rtl-optimization/48575: RTL vector patterns are limited to 26 elements
Date: Wed, 25 May 2011 23:09:00 -0000 [thread overview]
Message-ID: <BANLkTi=TRioCetObFoeFxwLKMK0j5uBH-A@mail.gmail.com> (raw)
In-Reply-To: <87mxiamsft.fsf@firetop.home>
On Wed, May 25, 2011 at 1:33 PM, Richard Sandiford
<rdsandiford@googlemail.com> wrote:
> "H.J. Lu" <hjl.tools@gmail.com> writes:
>> On Wed, May 25, 2011 at 7:47 AM, Richard Sandiford
>> <richard.sandiford@linaro.org> wrote:
>>> "H.J. Lu" <hjl.tools@gmail.com> writes:
>>>> No one is listed to review genrecog.c. Could global reviewers comment
>>>> on my patch?
>>>
>>> FWIW, one argument against this form of the change:
>>>
>>> http://gcc.gnu.org/ml/gcc-patches/2011-03/msg02159.html
>>
>> What you suggested is quite intrusive. I don't believe my approach
>> is more "hackish"/(ASCII-specific) than what we have today.
>
> OK, I suppose I should back my objection up with a patch.
> Rather than use strings, it uses a one-to-one mapping between
> positions and position objects. I agree it's more intrusive,
> but it's not that much more code. It also makes some operations
> cheaper.
>
> I diffed the old and new insn-recog.cs on x86_64-linux-gnu.
> The only difference was the removal of some:
>
> tem = peep2_next_insn (0);
> x1 = PATTERN (tem);
>
> sequences. In the old code, these came from make_insn_sequence
> using 'A' as the c_test position for single-instruction peepholes.
> Elsewhere we try to avoid calling peep2_next_insn (0), because its
> pattern is already available as x0, so I think this is an improvement.
> ("tem" and "x1" aren't part of the .md file interface, and AFAICT,
> no .md files are sneakily using them regardless.)
>
> Bootstrapped & regresion-tested on x86_64-linux-gnu. OK to install?
>
> Is it OK to remove the static forward declarations too?
>
> Richard
>
>
> gcc/
> PR rtl-optimization/48575
> * genrecog.c (position_type): New enum.
> (position): New structure.
> (decision): Use position structure instead of a string.
> (root_pos, peep2_insn_pos_list): New variables.
> (next_position, compare_positions): New functions.
> (new_decision): Use position structures instead of strings.
> (maybe_both_true): Likewise.
> (change_state): Likewise.
> (write_tree): Likewise.
> (make_insn_sequence): Likewise.
>
Appreciate it.
Thanks.
--
H.J.
next prev parent reply other threads:[~2011-05-25 21:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-18 16:52 H.J. Lu
2011-05-25 15:20 ` Richard Sandiford
2011-05-25 15:30 ` H.J. Lu
2011-05-25 22:20 ` Richard Sandiford
2011-05-25 23:09 ` H.J. Lu [this message]
2011-05-25 23:48 ` Mike Stump
2011-05-26 0:17 ` Bernd Schmidt
2011-05-26 21:22 ` Richard Sandiford
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='BANLkTi=TRioCetObFoeFxwLKMK0j5uBH-A@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=davem@redhat.com \
--cc=dnovillo@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gnu@the-meissners.org \
--cc=ian@airs.com \
--cc=jason@redhat.com \
--cc=law@redhat.com \
--cc=rdsandiford@googlemail.com \
--cc=richard.sandiford@linaro.org \
--cc=wilson@tuliptree.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).