public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sandra at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/113904] [OpenMP][5.0][5.1] Dynamic context selector 'user={condition(expr)}' not handled
Date: Tue, 13 Feb 2024 21:06:21 +0000	[thread overview]
Message-ID: <bug-113904-4-llKF6gcaia@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113904-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113904

--- Comment #4 from sandra at gcc dot gnu.org ---
Dynamic selectors are completely broken on mainline, since the patches that at
least partially implements this feature for metadirectives has not been
approved or committed yet.  I'm also very much aware that there is not even a
proposed patch to make this work for "declare variant" yet, although the
metadirectives work provides the underlying primitives that ought to be
adaptable for "declare variant" as well.

I suggest not messing around with incremental fixes meanwhile that would step
on the already-posted patches which cannot be considered until GCC 14 has
branched.

https://gcc.gnu.org/pipermail/gcc-patches/2024-January/642005.html

  parent reply	other threads:[~2024-02-13 21:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-13 11:26 [Bug middle-end/113904] New: " burnus at gcc dot gnu.org
2024-02-13 17:32 ` [Bug middle-end/113904] " burnus at gcc dot gnu.org
2024-02-13 19:56 ` cvs-commit at gcc dot gnu.org
2024-02-13 20:29 ` burnus at gcc dot gnu.org
2024-02-13 21:06 ` sandra at gcc dot gnu.org [this message]
2024-04-11  4:51 ` sandra at gcc dot gnu.org
2024-04-12  3:00 ` sandra at gcc dot gnu.org
2024-05-14  0:44 ` sandra at gcc dot gnu.org

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=bug-113904-4-llKF6gcaia@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).