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 r13-6863] Daily bump. Date: Sun, 26 Mar 2023 00:18:11 +0000 (GMT) [thread overview] Message-ID: <20230326001811.095873858D1E@sourceware.org> (raw) https://gcc.gnu.org/g:810b924f75df6abb5235796697249072dbd9affd commit r13-6863-g810b924f75df6abb5235796697249072dbd9affd Author: GCC Administrator <gccadmin@gcc.gnu.org> Date: Sun Mar 26 00:16:45 2023 +0000 Daily bump. Diff: --- gcc/ChangeLog | 15 +++++++++++++++ gcc/DATESTAMP | 2 +- gcc/fortran/ChangeLog | 5 +++++ gcc/testsuite/ChangeLog | 25 +++++++++++++++++++++++++ libcpp/ChangeLog | 6 ++++++ 5 files changed, 52 insertions(+), 1 deletion(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index b732fa6d2c9..7723d435b5c 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,18 @@ +2023-03-25 David Malcolm <dmalcolm@redhat.com> + + PR analyzer/109098 + * diagnostic-format-sarif.cc (read_until_eof): Delete. + (maybe_read_file): Delete. + (sarif_builder::maybe_make_artifact_content_object): Use + get_source_file_content rather than maybe_read_file. + Reject it if it's not valid UTF-8. + * input.cc (file_cache_slot::get_full_file_content): New. + (get_source_file_content): New. + (selftest::check_cpp_valid_utf8_p): New. + (selftest::test_cpp_valid_utf8_p): New. + (selftest::input_cc_tests): Call selftest::test_cpp_valid_utf8_p. + * input.h (get_source_file_content): New prototype. + 2023-03-24 David Malcolm <dmalcolm@redhat.com> * doc/analyzer.texi (Debugging the Analyzer): Add notes on useful diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP index 3c8c315bc19..ba111ba97d1 100644 --- a/gcc/DATESTAMP +++ b/gcc/DATESTAMP @@ -1 +1 @@ -20230325 +20230326 diff --git a/gcc/fortran/ChangeLog b/gcc/fortran/ChangeLog index 0d7cbfdf8c0..e93eeb51129 100644 --- a/gcc/fortran/ChangeLog +++ b/gcc/fortran/ChangeLog @@ -1,3 +1,8 @@ +2023-03-25 Harald Anlauf <anlauf@gmx.de> + + PR fortran/104321 + * trans-decl.cc (gfc_conv_cfi_to_gfc): Remove dead code. + 2023-03-24 Harald Anlauf <anlauf@gmx.de> * expr.cc (free_expr0): Free also BOZ strings as part of an expression. diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog index 27cbce430b8..6de4b3f3be1 100644 --- a/gcc/testsuite/ChangeLog +++ b/gcc/testsuite/ChangeLog @@ -1,3 +1,28 @@ +2023-03-25 David Malcolm <dmalcolm@redhat.com> + + PR analyzer/109098 + * c-c++-common/diagnostic-format-sarif-file-1.c: Add + verify-sarif-file directive. + * c-c++-common/diagnostic-format-sarif-file-2.c: Likewise. + * c-c++-common/diagnostic-format-sarif-file-3.c: Likewise. + * c-c++-common/diagnostic-format-sarif-file-4.c: Likewise. + * c-c++-common/diagnostic-format-sarif-file-Wbidi-chars.c: New + test case, adapted from Wbidi-chars-1.c. + * c-c++-common/diagnostic-format-sarif-file-bad-utf8-pr109098-1.c: + New test case. + * c-c++-common/diagnostic-format-sarif-file-bad-utf8-pr109098-2.c: + New test case. + * c-c++-common/diagnostic-format-sarif-file-bad-utf8-pr109098-3.c: + New test case, adapted from cpp/Winvalid-utf8-1.c. + * c-c++-common/diagnostic-format-sarif-file-valid-CP850.c: New + test case, adapted from gcc.dg/diagnostic-input-charset-1.c. + * gcc.dg/plugin/crash-test-ice-sarif.c: Add verify-sarif-file + directive. + * gcc.dg/plugin/crash-test-write-though-null-sarif.c: Likewise. + * gcc.dg/plugin/diagnostic-test-paths-5.c: Likewise. + * lib/scansarif.exp (verify-sarif-file): New procedure. + * lib/verify-sarif-file.py: New support script. + 2023-03-24 Patrick Palka <ppalka@redhat.com> PR c++/106969 diff --git a/libcpp/ChangeLog b/libcpp/ChangeLog index e1410129679..8510dc20bed 100644 --- a/libcpp/ChangeLog +++ b/libcpp/ChangeLog @@ -1,3 +1,9 @@ +2023-03-25 David Malcolm <dmalcolm@redhat.com> + + PR analyzer/109098 + * charset.cc (cpp_valid_utf8_p): New function. + * include/cpplib.h (cpp_valid_utf8_p): New prototype. + 2023-03-16 Jakub Jelinek <jakub@redhat.com> * makeucnid.cc (write_copyright): Update Unicode copyright years
reply other threads:[~2023-03-26 0:18 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=20230326001811.095873858D1E@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).