public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@gmail.com>
To: James Greenhalgh <james.greenhalgh@arm.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH/AARCH64] Remove index from AARCH64_FUSION_PAIR
Date: Wed, 19 Aug 2015 13:00:00 -0000	[thread overview]
Message-ID: <CA+=Sn1=yFmnww+v1ypNNb-ESpQDc=V0CTe=D2QhUgovoAU=WGQ@mail.gmail.com> (raw)
In-Reply-To: <20150819113926.GA3411@e107456-lin.cambridge.arm.com>

On Wed, Aug 19, 2015 at 7:39 PM, James Greenhalgh
<james.greenhalgh@arm.com> wrote:
> On Wed, Aug 19, 2015 at 12:11:04PM +0100, Andrew Pinski wrote:
>>     Instead of doing an explicit index in aarch64-fusion-pairs.def, we
>>     should have an enum which does the index instead.  This allows
>>     you to add/remove them without worrying about the order being
>>     correct and having holes or worry about merge conflicts.
>>
>>     OK? Bootstrapped and tested on aarch64-linux-gnu with no regressions.
>>
>
> Looks good, it would be good to expand this patch to get rid of the
> messy way we build the AARCH64_FUSE_ALL macro:
>
>> /* Hacky macro to build AARCH64_FUSE_ALL.  The sequence below expands
>>    to:
>>    AARCH64_FUSE_ALL = 0 | AARCH64_FUSE_index1 | AARCH64_FUSE_index2 ...  */
>> #undef AARCH64_FUSION_PAIR
>> #define AARCH64_FUSION_PAIR(x, name, y) \
>>   | AARCH64_FUSE_##name
>>
>>   AARCH64_FUSE_ALL = 0
>> #include "aarch64-fusion-pairs.def"
>
> We should now be able to do something like:
>
>   AARCH64_FUSE_ALL = ((1 << AARCH64_FUSE_index_END) - 1)
>
> Right?

Yes I actually thought of that after I had submitted the patch.

>
> If so, could you respin with that change?

Respinning this patch and the one for AARCH64_EXTRA_TUNING_OPTION.

Thanks,
Andrew

>
> Thanks,
> James
>
>
>> diff --git a/gcc/config/aarch64/aarch64-fusion-pairs.def b/gcc/config/aarch64/aarch64-fusion-pairs.def
>> index a7b00f6..53bbef4 100644
>> --- a/gcc/config/aarch64/aarch64-fusion-pairs.def
>> +++ b/gcc/config/aarch64/aarch64-fusion-pairs.def
>> @@ -20,19 +20,17 @@
>>  /* Pairs of instructions which can be fused. before including this file,
>>     define a macro:
>>
>> -     AARCH64_FUSION_PAIR (name, internal_name, index_bit)
>> +     AARCH64_FUSION_PAIR (name, internal_name)
>>
>>     Where:
>>
>>       NAME is a string giving a friendly name for the instructions to fuse.
>>       INTERNAL_NAME gives the internal name suitable for appending to
>> -     AARCH64_FUSE_ to give an enum name.
>> -     INDEX_BIT is the bit to set in the bitmask of supported fusion
>> -     operations.  */
>> -
>> -AARCH64_FUSION_PAIR ("mov+movk", MOV_MOVK, 0)
>> -AARCH64_FUSION_PAIR ("adrp+add", ADRP_ADD, 1)
>> -AARCH64_FUSION_PAIR ("movk+movk", MOVK_MOVK, 2)
>> -AARCH64_FUSION_PAIR ("adrp+ldr", ADRP_LDR, 3)
>> -AARCH64_FUSION_PAIR ("cmp+branch", CMP_BRANCH, 4)
>> +     AARCH64_FUSE_ to give an enum name. */
>> +
>> +AARCH64_FUSION_PAIR ("mov+movk", MOV_MOVK)
>> +AARCH64_FUSION_PAIR ("adrp+add", ADRP_ADD)
>> +AARCH64_FUSION_PAIR ("movk+movk", MOVK_MOVK)
>> +AARCH64_FUSION_PAIR ("adrp+ldr", ADRP_LDR)
>> +AARCH64_FUSION_PAIR ("cmp+branch", CMP_BRANCH)
>>
>> diff --git a/gcc/config/aarch64/aarch64-protos.h b/gcc/config/aarch64/aarch64-protos.h
>> index 0b09d49..c4c1817 100644
>> --- a/gcc/config/aarch64/aarch64-protos.h
>> +++ b/gcc/config/aarch64/aarch64-protos.h
>> @@ -201,8 +201,18 @@ struct tune_params
>>    unsigned int extra_tuning_flags;
>>  };
>>
>> -#define AARCH64_FUSION_PAIR(x, name, index) \
>> -  AARCH64_FUSE_##name = (1 << index),
>> +#define AARCH64_FUSION_PAIR(x, name) \
>> +  AARCH64_FUSE_##name##_index,
>> +/* Supported fusion operations.  */
>> +enum aarch64_fusion_pairs_index
>> +{
>> +#include "aarch64-fusion-pairs.def"
>> +  AARCH64_FUSE_index_END
>> +};
>> +#undef AARCH64_FUSION_PAIR
>> +
>> +#define AARCH64_FUSION_PAIR(x, name) \
>> +  AARCH64_FUSE_##name = (1 << AARCH64_FUSE_##name##_index),
>>  /* Supported fusion operations.  */
>>  enum aarch64_fusion_pairs
>>  {
>> @@ -213,7 +223,7 @@ enum aarch64_fusion_pairs
>>     to:
>>     AARCH64_FUSE_ALL = 0 | AARCH64_FUSE_index1 | AARCH64_FUSE_index2 ...  */
>>  #undef AARCH64_FUSION_PAIR
>> -#define AARCH64_FUSION_PAIR(x, name, y) \
>> +#define AARCH64_FUSION_PAIR(x, name) \
>>    | AARCH64_FUSE_##name
>>
>>    AARCH64_FUSE_ALL = 0
>> diff --git a/gcc/config/aarch64/aarch64.c b/gcc/config/aarch64/aarch64.c
>> index aa268ae..162e25e 100644
>> --- a/gcc/config/aarch64/aarch64.c
>> +++ b/gcc/config/aarch64/aarch64.c
>> @@ -172,7 +172,7 @@ struct aarch64_flag_desc
>>    unsigned int flag;
>>  };
>>
>> -#define AARCH64_FUSION_PAIR(name, internal_name, y) \
>> +#define AARCH64_FUSION_PAIR(name, internal_name) \
>>    { name, AARCH64_FUSE_##internal_name },
>>  static const struct aarch64_flag_desc aarch64_fusible_pairs[] =
>>  {
>

      reply	other threads:[~2015-08-19 12:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-19 11:15 Andrew Pinski
2015-08-19 12:11 ` James Greenhalgh
2015-08-19 13:00   ` Andrew Pinski [this message]

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='CA+=Sn1=yFmnww+v1ypNNb-ESpQDc=V0CTe=D2QhUgovoAU=WGQ@mail.gmail.com' \
    --to=pinskia@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=james.greenhalgh@arm.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).