public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: GCC Administrator <gccadmin@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r12-8649] Daily bump. Date: Tue, 2 Aug 2022 00:19:55 +0000 (GMT) [thread overview] Message-ID: <20220802001955.C174B3858028@sourceware.org> (raw) https://gcc.gnu.org/g:e04785d99d52445fd17357c22a07dd3a62f56de3 commit r12-8649-ge04785d99d52445fd17357c22a07dd3a62f56de3 Author: GCC Administrator <gccadmin@gcc.gnu.org> Date: Tue Aug 2 00:19:17 2022 +0000 Daily bump. Diff: --- gcc/DATESTAMP | 2 +- gcc/c/ChangeLog | 9 +++++++++ gcc/testsuite/ChangeLog | 11 +++++++++++ libcpp/ChangeLog | 10 ++++++++++ libgomp/ChangeLog | 9 +++++++++ 5 files changed, 40 insertions(+), 1 deletion(-) diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP index ed14e56feeb..dd67218a4ee 100644 --- a/gcc/DATESTAMP +++ b/gcc/DATESTAMP @@ -1 +1 @@ -20220801 +20220802 diff --git a/gcc/c/ChangeLog b/gcc/c/ChangeLog index 6d4f3ed523d..02eade0c051 100644 --- a/gcc/c/ChangeLog +++ b/gcc/c/ChangeLog @@ -1,3 +1,12 @@ +2022-08-01 Lewis Hyatt <lhyatt@gmail.com> + + Backported from master: + 2022-07-10 Lewis Hyatt <lhyatt@gmail.com> + + PR preprocessor/97498 + * c-parser.cc (c_parser_pragma): Set input_location to the + location of the pragma, rather than the start of the line. + 2022-05-06 Release Manager * GCC 12.1.0 released. diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog index 12019bbb0fa..c9535e8d9b9 100644 --- a/gcc/testsuite/ChangeLog +++ b/gcc/testsuite/ChangeLog @@ -1,3 +1,14 @@ +2022-08-01 Lewis Hyatt <lhyatt@gmail.com> + + Backported from master: + 2022-07-10 Lewis Hyatt <lhyatt@gmail.com> + + PR preprocessor/97498 + * c-c++-common/pr97498.c: New test. + * c-c++-common/gomp/pragma-3.c: Adapt for improved warning locations. + * c-c++-common/gomp/pragma-5.c: Likewise. + * gcc.dg/pragma-message.c: Likewise. + 2022-07-30 Jakub Jelinek <jakub@redhat.com> Backported from master: diff --git a/libcpp/ChangeLog b/libcpp/ChangeLog index 86b56ad24b9..70d96df9d4e 100644 --- a/libcpp/ChangeLog +++ b/libcpp/ChangeLog @@ -1,3 +1,13 @@ +2022-08-01 Lewis Hyatt <lhyatt@gmail.com> + + Backported from master: + 2022-07-10 Lewis Hyatt <lhyatt@gmail.com> + + PR preprocessor/97498 + * directives.cc (destringize_and_run): Override the location of + the CPP_PRAGMA token from a _Pragma directive to the location of + the expansion point, as is done for the tokens lexed from it. + 2022-05-30 Jakub Jelinek <jakub@redhat.com> Backported from master: diff --git a/libgomp/ChangeLog b/libgomp/ChangeLog index 1620e08545d..4307e962b3d 100644 --- a/libgomp/ChangeLog +++ b/libgomp/ChangeLog @@ -1,3 +1,12 @@ +2022-08-01 Lewis Hyatt <lhyatt@gmail.com> + + Backported from master: + 2022-07-10 Lewis Hyatt <lhyatt@gmail.com> + + * testsuite/libgomp.oacc-c-c++-common/reduction-5.c: Adapt for + improved warning locations. + * testsuite/libgomp.oacc-c-c++-common/vred2d-128.c: Likewise. + 2022-07-30 Jakub Jelinek <jakub@redhat.com> Backported from master:
reply other threads:[~2022-08-02 0:19 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220802001955.C174B3858028@sourceware.org \ --to=gccadmin@gcc.gnu.org \ --cc=gcc-cvs@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).