From: Dave Love <dave.love@manchester.ac.uk>
To: fortran@gcc.gnu.org
Subject: Re: adding attributes
Date: Mon, 07 Nov 2022 11:06:18 +0000 [thread overview]
Message-ID: <87y1sn81n9.fsf@manchester.ac.uk> (raw)
In-Reply-To: <f38c13e5-c825-2c8c-b41c-9e4a61bf3c25@netcologne.de>
Thomas Koenig via Fortran <fortran@gcc.gnu.org> writes:
> Hi Bernhard,
>
>> If you think that we want to add support for that attribute, i can
>> submit a proper patch. Just let me know please.
>
> I think this attribute makes sense, especially if people want to
> compile once and then port to different architectures.
>
> So, yes please submit a patch, if you would be so kind :-)
>
> Best regards
>
> Thomas
I'll make a list of others I think would be useful for consideration. I
should probably have looked at what similar facilities proprietary
compilers provide.
I should say the intent of optimization-related attributes would be to
encourage adding them to known performance-sensitive kernels, and
potentially avoid having to write C. However, I doubt I can persuade
the people who are convinced of the great superiority of ifort, and the
desirability of always adding -axCORE-AVX512, without measuring or
understanding GCC options.
I think an equivalent of "#pragma GCC optimize" could be useful too. I
don't have a specific case in mind, but an example might be where you
need localized standard-conforming arithmetic, but other parts of the
program benefit from -ffast-math.
next prev parent reply other threads:[~2022-11-07 11:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 14:35 Dave Love
2022-10-30 7:48 ` Bernhard Reutner-Fischer
2022-10-31 21:19 ` Dave Love
2022-11-02 23:19 ` Bernhard Reutner-Fischer
2022-11-04 20:59 ` Bernhard Reutner-Fischer
2022-11-05 7:40 ` Thomas Koenig
2022-11-05 10:54 ` Bernhard Reutner-Fischer
2022-11-06 13:44 ` Thomas Koenig
2022-11-07 11:06 ` Dave Love [this message]
2023-02-24 12:24 ` Dave Love
2022-11-07 11:04 ` Dave Love
2022-11-10 12:25 ` Bernhard Reutner-Fischer
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=87y1sn81n9.fsf@manchester.ac.uk \
--to=dave.love@manchester.ac.uk \
--cc=fortran@gcc.gnu.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).