From: Tobias Burnus <tburnus@baylibre.com>
To: Jakub Jelinek <jakub@redhat.com>, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch] OpenMP: Add -fopenmp-force-usm mode
Date: Wed, 29 May 2024 08:49:01 +0200 [thread overview]
Message-ID: <cacf56c8-0cba-4fe7-b952-c30aee11ecc8@baylibre.com> (raw)
In-Reply-To: <ZlbL5irt7TBRc/Ph@tucnak>
[-- Attachment #1: Type: text/plain, Size: 576 bytes --]
Jakub Jelinek wrote:
> I mean, if we want to add something, maybe better would an -include like
> option that instead of including a file includes it directly.
> gcc --include-inline '#pragma omp requires unified_shared_memory' ...
Likewise for Fortran, but there the question is whether it should be in
the use-stmt, import-stmt, implicit-part or declaration-part; I guess
having one --include-inline-use-stmt and --include-inline-declaration
would make sense …
And, I guess, multiple flags should be permitted, which can then be
processed as separate lines.
Tobias
next prev parent reply other threads:[~2024-05-29 6:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 19:23 Tobias Burnus
2024-05-29 6:26 ` Jakub Jelinek
2024-05-29 6:32 ` Jakub Jelinek
2024-05-29 6:49 ` Tobias Burnus [this message]
2024-05-29 6:52 ` Jakub Jelinek
2024-05-29 6:41 ` Tobias Burnus
2024-05-29 6:50 ` Jakub Jelinek
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=cacf56c8-0cba-4fe7-b952-c30aee11ecc8@baylibre.com \
--to=tburnus@baylibre.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.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).