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 middle-end/110639] [OpenMP][5.1] Predefined firstprivate for pointers - attachment missing Date: Tue, 05 Dec 2023 13:57:29 +0000 [thread overview] Message-ID: <bug-110639-4-G8bD3TnI4N@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110639-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110639 --- Comment #3 from Tobias Burnus <burnus at gcc dot gnu.org> --- Created attachment 56804 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56804&action=edit gimplify.cc patch to ensure that GOVD_MAP_0LEN_ARRAY comes last (does not fix the issue) I tried the attached patch see whether it fixes the problem. It doesn't as the pointer-lookup-for-attachment seems to happen in an earlier 'for' loop than the 'for' loop that does the actual mapping for clauses on the same 'target' directive (→ gomp_map_vars_internal). Thus, either this patch is not required - or it is only required in addition; in any case, it seems as if libgomp/target.c's gomp_map_vars_internal needs to be modified.
next prev parent reply other threads:[~2023-12-05 13:57 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-12 9:32 [Bug middle-end/110639] New: " burnus at gcc dot gnu.org 2023-11-21 15:57 ` [Bug middle-end/110639] " burnus at gcc dot gnu.org 2023-11-21 16:31 ` burnus at gcc dot gnu.org 2023-12-05 13:57 ` burnus at gcc dot gnu.org [this message] 2023-12-06 15:43 ` burnus at gcc dot gnu.org 2023-12-11 11:57 ` burnus 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-110639-4-G8bD3TnI4N@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).