public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/95270] OpenACC 'enter data attach' looks up target memory object displaced by pointer size
Date: Mon, 13 Jul 2020 17:14:04 +0000	[thread overview]
Message-ID: <bug-95270-4-4hTQikDqIf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95270-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Julian Brown
<jules@gcc.gnu.org>:

https://gcc.gnu.org/g:2974e1eee053496e1d43f7f2e62f5feac2aa0315

commit r10-8475-g2974e1eee053496e1d43f7f2e62f5feac2aa0315
Author: Julian Brown <julian@codesourcery.com>
Date:   Tue Jun 9 06:21:34 2020 -0700

    openacc: Set bias to zero for explicit attach/detach clauses in C and C++

    This is a fix for the pointer (or array) size inadvertently being used
    for the bias with attach and detach mapping kinds, for both C and C++.

    2020-07-09  Julian Brown  <julian@codesourcery.com>
                Thomas Schwinge  <thomas@codesourcery.com>

    gcc/c/
            PR middle-end/95270
            * c-typeck.c (c_finish_omp_clauses): Set OMP_CLAUSE_SIZE (bias) to
zero
            for standalone attach/detach clauses.

    gcc/cp/
            PR middle-end/95270
            * semantics.c (finish_omp_clauses): Likewise.

    include/
            PR middle-end/95270
            * gomp-constants.h (gomp_map_kind): Expand comment for
attach/detach
            mapping kinds.

    gcc/testsuite/
            PR middle-end/95270
            * c-c++-common/goacc/mdc-1.c: Update expected dump output for zero
            bias.

    libgomp/
            PR middle-end/95270
            * testsuite/libgomp.oacc-c-c++-common/pr95270-1.c: New test.
            * testsuite/libgomp.oacc-c-c++-common/pr95270-2.c: New test.

    (cherry picked from commit 0d00fe404c162ad0cf922ca8455aa23a74042b63)

  parent reply	other threads:[~2020-07-13 17:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-22 13:22 [Bug middle-end/95270] New: OpenACC 'enter data attach(data_p)' fails for 'int *data_p' tschwinge at gcc dot gnu.org
2020-06-08 18:53 ` [Bug middle-end/95270] OpenACC 'enter data attach' looks up target memory object displaced by pointer size tschwinge at gcc dot gnu.org
2020-06-08 19:25 ` jules at gcc dot gnu.org
2020-07-09 22:44 ` cvs-commit at gcc dot gnu.org
2020-07-13 17:14 ` cvs-commit at gcc dot gnu.org [this message]
2022-01-09  0:33 ` pinskia 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-95270-4-4hTQikDqIf@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).