public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Hongyu Wang <wwwhhhyyy333@gmail.com>
To: Uros Bizjak <ubizjak@gmail.com>
Cc: Hongyu Wang <hongyu.wang@intel.com>,
	gcc-patches@gcc.gnu.org, hongtao.liu@intel.com
Subject: Re: [PATCH] i386: Sync tune_string with arch_string for target attribute arch=*
Date: Tue, 27 Jun 2023 13:43:24 +0800	[thread overview]
Message-ID: <CA+OydWmA2ayyVa9PHxYvbW3taDiiDhS0r7P4kuJMCHcLhV4jrQ@mail.gmail.com> (raw)
In-Reply-To: <CAFULd4b4RNWX4+atAi8Hv-O7Y24KLS4qWaTOkGddxO4gpzOWNw@mail.gmail.com>

Thanks, I'll backport it down to GCC10 after this passed all bootstrap/regtest.

Uros Bizjak via Gcc-patches <gcc-patches@gcc.gnu.org> 于2023年6月26日周一 14:05写道:
>
> On Mon, Jun 26, 2023 at 4:31 AM Hongyu Wang <hongyu.wang@intel.com> wrote:
> >
> > Hi,
> >
> > For function with target attribute arch=*, current logic will set its
> > tune to -mtune from command line so all target_clones will get same
> > tuning flags which would affect the performance for each clone. Override
> > tune with arch if tune was not explicitly specified to get proper tuning
> > flags for target_clones.
> >
> > Bootstrapped/regtested on x86_64-pc-linux-gnu{-m32,}
> >
> > Ok for trunk and backport to active release branches?
> >
> > gcc/ChangeLog:
> >
> >         * config/i386/i386-options.cc (ix86_valid_target_attribute_tree):
> >         Override tune_string with arch_string if tune_string is not
> >         explicitly specified.
> >
> > gcc/testsuite/ChangeLog:
> >
> >         * gcc.target/i386/mvc17.c: New test.
>
> LGTM.
>
> Thanks,
> Uros.
>
> > ---
> >  gcc/config/i386/i386-options.cc       |  6 +++++-
> >  gcc/testsuite/gcc.target/i386/mvc17.c | 11 +++++++++++
> >  2 files changed, 16 insertions(+), 1 deletion(-)
> >  create mode 100644 gcc/testsuite/gcc.target/i386/mvc17.c
> >
> > diff --git a/gcc/config/i386/i386-options.cc b/gcc/config/i386/i386-options.cc
> > index 2cb0bddcd35..7f593cebe76 100644
> > --- a/gcc/config/i386/i386-options.cc
> > +++ b/gcc/config/i386/i386-options.cc
> > @@ -1400,7 +1400,11 @@ ix86_valid_target_attribute_tree (tree fndecl, tree args,
> >        if (option_strings[IX86_FUNCTION_SPECIFIC_TUNE])
> >         opts->x_ix86_tune_string
> >           = ggc_strdup (option_strings[IX86_FUNCTION_SPECIFIC_TUNE]);
> > -      else if (orig_tune_defaulted)
> > +      /* If we have explicit arch string and no tune string specified, set
> > +        tune_string to NULL and later it will be overriden by arch_string
> > +        so target clones can get proper optimization.  */
> > +      else if (option_strings[IX86_FUNCTION_SPECIFIC_ARCH]
> > +              || orig_tune_defaulted)
> >         opts->x_ix86_tune_string = NULL;
> >
> >        /* If fpmath= is not set, and we now have sse2 on 32-bit, use it.  */
> > diff --git a/gcc/testsuite/gcc.target/i386/mvc17.c b/gcc/testsuite/gcc.target/i386/mvc17.c
> > new file mode 100644
> > index 00000000000..2c7cc2fdace
> > --- /dev/null
> > +++ b/gcc/testsuite/gcc.target/i386/mvc17.c
> > @@ -0,0 +1,11 @@
> > +/* { dg-do compile } */
> > +/* { dg-require-ifunc "" } */
> > +/* { dg-options "-O2" } */
> > +/* { dg-final { scan-assembler-times "rep mov" 1 } } */
> > +
> > +__attribute__((target_clones("default","arch=icelake-server")))
> > +void
> > +foo (char *a, char *b, int size)
> > +{
> > +  __builtin_memcpy (a, b, size & 0x7F);
> > +}
> > --
> > 2.31.1
> >

  reply	other threads:[~2023-06-27  5:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-26  2:29 Hongyu Wang
2023-06-26  6:04 ` Uros Bizjak
2023-06-27  5:43   ` Hongyu Wang [this message]
2023-06-28  1:53     ` Hongyu Wang

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+OydWmA2ayyVa9PHxYvbW3taDiiDhS0r7P4kuJMCHcLhV4jrQ@mail.gmail.com \
    --to=wwwhhhyyy333@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hongtao.liu@intel.com \
    --cc=hongyu.wang@intel.com \
    --cc=ubizjak@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).