public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgomp/109875] [OpenMP] nteams-var / OMP_NUM_TEAMS → ICV not passed to the device / default value Date: Sun, 21 May 2023 18:56:52 +0000 [thread overview] Message-ID: <bug-109875-4-H1fEXeCZUz@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109875-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109875 Tobias Burnus <burnus at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #4 from Tobias Burnus <burnus at gcc dot gnu.org> --- FIXED the issue that the number of teams in target regions exceeded the limit set by the nteams-var ICV. (→ GCC mainline/14). Unsolved: Checking whether the omp_get_max_teams() returns the proper value or not. — This depends on the outcome of OpenMP Spec Issue 3619. Still close this issue as a likely solution could be to keep the current implementation (init = 0, return value of the ICV, which is 0), possibly except for permitting 0 for the env var (0 is already accepted for omp_set_num_devices), but the outcome should be tracked in a new issue.
prev parent reply other threads:[~2023-05-21 18:56 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-16 17:39 [Bug libgomp/109875] New: " burnus at gcc dot gnu.org 2023-05-17 9:47 ` [Bug libgomp/109875] " burnus at gcc dot gnu.org 2023-05-17 10:11 ` burnus at gcc dot gnu.org 2023-05-21 18:44 ` cvs-commit at gcc dot gnu.org 2023-05-21 18:56 ` burnus at gcc dot gnu.org [this message]
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-109875-4-H1fEXeCZUz@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: linkBe 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).