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 fortran/96668] [OpenMP] Re-mapping allocated but previously unallocated allocatable does not work
Date: Tue, 15 Sep 2020 19:44:39 +0000 [thread overview]
Message-ID: <bug-96668-4-J9Tlua7N74@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96668-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96668
--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tobias Burnus <burnus@gcc.gnu.org>:
https://gcc.gnu.org/g:1b9bdd52037061d7a5bd77d177b060c93c528a5d
commit r11-3211-g1b9bdd52037061d7a5bd77d177b060c93c528a5d
Author: Tobias Burnus <tobias@codesourcery.com>
Date: Tue Sep 15 21:28:40 2020 +0200
libgomp/target.c: Silence -Wuninitialized warning
libgomp/ChangeLog:
PR fortran/96668
* target.c (gomp_map_vars_internal): Initialize has_nullptr.
next prev parent reply other threads:[~2020-09-15 19:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 6:56 [Bug fortran/96668] New: " burnus at gcc dot gnu.org
2020-08-18 8:59 ` [Bug fortran/96668] " burnus at gcc dot gnu.org
2020-08-18 10:26 ` cltang at gcc dot gnu.org
2020-08-18 16:11 ` kargl at gcc dot gnu.org
2020-08-18 17:02 ` burnus at gcc dot gnu.org
2020-09-15 7:25 ` cvs-commit at gcc dot gnu.org
2020-09-15 7:39 ` burnus at gcc dot gnu.org
2020-09-15 19:44 ` cvs-commit at gcc dot gnu.org [this message]
2022-03-10 10:22 ` burnus at gcc dot gnu.org
2022-11-02 20:03 ` cvs-commit 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-96668-4-J9Tlua7N74@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).