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/108558] OpenMP/Fortran 'has_device_addr' clause getting lost? Date: Fri, 27 Jan 2023 10:34:21 +0000 [thread overview] Message-ID: <bug-108558-4-x7YhXK87WA@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108558-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108558 --- Comment #3 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:2325c8920bbc99edcc9fffaa79577c528df41eb8 commit r13-5438-g2325c8920bbc99edcc9fffaa79577c528df41eb8 Author: Tobias Burnus <tobias@codesourcery.com> Date: Fri Jan 27 11:32:19 2023 +0100 OpenMP/Fortran: Fix has_device_addr clause splitting [PR108558] gcc/fortran/ChangeLog: PR fortran/108558 * trans-openmp.cc (gfc_split_omp_clauses): Handle has_device_addr. libgomp/ChangeLog: PR fortran/108558 * testsuite/libgomp.fortran/has_device_addr.f90: New test.
next prev parent reply other threads:[~2023-01-27 10:34 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-26 12:02 [Bug fortran/108558] New: " tschwinge at gcc dot gnu.org 2023-01-26 12:36 ` [Bug fortran/108558] " burnus at gcc dot gnu.org 2023-01-26 13:46 ` tschwinge at gcc dot gnu.org 2023-01-27 10:34 ` cvs-commit at gcc dot gnu.org [this message] 2023-01-27 10:48 ` burnus at gcc dot gnu.org 2023-01-30 8:57 ` cvs-commit at gcc dot gnu.org 2023-01-30 9:22 ` 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-108558-4-x7YhXK87WA@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).