From: GT <tnggil@protonmail.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
"segher@kernel.crashing.org" <segher@kernel.crashing.org>,
"dje.gcc@gmail.com" <dje.gcc@gmail.com>,
"wschmidt@linux.ibm.com" <wschmidt@linux.ibm.com>,
"tuliom@linux.ibm.com" <tuliom@linux.ibm.com>,
"tnggil@protonmail.com" <tnggil@protonmail.com>
Subject: Re: [RFC PATCH v1 1/1] PPC64: Implement POWER Architecture Vector Function ABI.
Date: Thu, 20 Aug 2020 19:31:50 +0000 [thread overview]
Message-ID: <e34ehuMYyRSj40Me93jCrAlyb2o2Wif-j0xo3aKYLqIB8HzRRDcPCvyKBy2BNPY2LrwoLKu38EwfS47-7J4KTjuSyl-AHIGyW_YayVceXTQ=@protonmail.com> (raw)
In-Reply-To: <20200813210059.GK2363@tucnak>
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Thursday, August 13, 2020 5:00 PM, Jakub Jelinek <jakub@redhat.com> wrote:
> On Thu, Aug 13, 2020 at 08:40:22PM +0000, GT wrote:
>
> > I'm looking at ix86_simd_clone_adjust and also aarch64_simd_clone_adjust. The latter is
> > much simpler and I see how I would add PPC attribute "vsx" similarly. If I was to follow
> > the ix86_simd_clone_adjust organization, then ix86_valid_target_attribute_p called near
> > the end of the function is a problem. Because it in turn calls
> > ix86_valid_target_attribute_tree and this last function doesn't have a similarly named
> > function in PPC code.
> > Also, once the attribute "vsx" is added, where is it used? I mean that in the sense of
> > where is execution conditioned on the definition of say, the "sse2" string in x86_64?
>
> You need to trigger what will the middle-end and backend do if you use
> explicit attribute((target ("vsx"))) on the function, so in the end it
> needs to do some parsing, create a TARGET_OPTION_NODE with the right option
> changes and put it to the function.
>
> Jakub
I'm still trying to understand why we need attribute((target("vsx"))).
https://gcc.gnu.org/onlinedocs/gcc/Common-Function-Attributes.html#Common-Function-Attributes
The documentation for target(string) states that the purpose is to allow a function to be
compiled with different target options than were specified on the command line. Why would we
want the vector version of say sinf to be compiled for a different target than the scalar sinf?
Bert.
next prev parent reply other threads:[~2020-08-20 19:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-07 20:35 Bert Tenjy
2020-08-07 20:59 ` Jakub Jelinek
2020-08-10 17:29 ` GT
2020-08-10 18:07 ` Jakub Jelinek
2020-08-13 20:40 ` GT
2020-08-13 21:00 ` Jakub Jelinek
2020-08-20 19:31 ` GT [this message]
2020-08-20 20:04 ` Jakub Jelinek
2020-08-20 20:29 ` Segher Boessenkool
2020-08-13 22:49 ` Segher Boessenkool
2020-08-17 17:44 ` GT
2020-08-17 21:28 ` Segher Boessenkool
2020-08-18 19:14 ` GT
2020-08-18 21:32 ` Segher Boessenkool
2020-08-20 16:19 ` GT
2020-08-20 17:48 ` Segher Boessenkool
2020-12-04 18:28 ` GT
2020-08-17 22:05 ` David Edelsohn
2020-08-17 23:06 ` Segher Boessenkool
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='e34ehuMYyRSj40Me93jCrAlyb2o2Wif-j0xo3aKYLqIB8HzRRDcPCvyKBy2BNPY2LrwoLKu38EwfS47-7J4KTjuSyl-AHIGyW_YayVceXTQ=@protonmail.com' \
--to=tnggil@protonmail.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=segher@kernel.crashing.org \
--cc=tuliom@linux.ibm.com \
--cc=wschmidt@linux.ibm.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).