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/98011] [OpenACC] 'gcc/fortran/scanner.c:load_line' should consider 'flag_openacc' in addition to 'flag_openmp' (and vice versa?)?
Date: Sun, 15 Oct 2023 21:12:15 +0000 [thread overview]
Message-ID: <bug-98011-4-nuq3ouq5wA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98011-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98011
--- Comment #5 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:643a5223f1a1860a88c215d715f079d7f846843c
commit r14-4651-g643a5223f1a1860a88c215d715f079d7f846843c
Author: Tobias Burnus <tobias@codesourcery.com>
Date: Sun Oct 15 23:10:17 2023 +0200
libgomp.texi: Update "Enabling OpenMP" + OpenACC / invoke.texi:
-fopenacc/-fopenmp update
The OpenACC specification does not mention the '!$ ' sentinel for
conditional
compilation and the feature was removed in r11-5572-g1d6f6ac693a860
for PR fortran/98011; update libgomp.texi for this and update a leftover
comment. - Additionally, some other updates are done as well.
libgomp/
* libgomp.texi (Enabling OpenMP): Update for C/C++ attributes;
improve wording especially for Fortran; mention -fopenmp-simd.
(Enabling OpenACC): Minor cleanup; remove conditional compilation
sentinel.
gcc/
* doc/invoke.texi (-fopenacc, -fopenmp, -fopenmp-simd): Use @samp
not
@code; document more completely the supported Fortran sentinels.
gcc/fortran
* scanner.cc (skip_free_comments, skip_fixed_comments): Remove
leftover 'OpenACC' from comments about OpenMP's conditional
compilation sentinel.
prev parent reply other threads:[~2023-10-15 21:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-26 10:59 [Bug fortran/98011] New: " tschwinge at gcc dot gnu.org
2020-11-26 11:41 ` [Bug fortran/98011] " burnus at gcc dot gnu.org
2020-11-26 11:59 ` burnus at gcc dot gnu.org
2020-11-30 14:37 ` cvs-commit at gcc dot gnu.org
2020-11-30 14:48 ` burnus at gcc dot gnu.org
2023-10-15 21:12 ` cvs-commit 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-98011-4-nuq3ouq5wA@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).