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-2583] Daily bump. Date: Mon, 12 Sep 2022 00:18:41 +0000 (GMT) [thread overview] Message-ID: <20220912001841.B7C7D3858C83@sourceware.org> (raw) https://gcc.gnu.org/g:5b9111db573c55dbe7730582d23d0e4c4959abf7 commit r13-2583-g5b9111db573c55dbe7730582d23d0e4c4959abf7 Author: GCC Administrator <gccadmin@gcc.gnu.org> Date: Mon Sep 12 00:17:04 2022 +0000 Daily bump. Diff: --- gcc/DATESTAMP | 2 +- gcc/analyzer/ChangeLog | 14 ++++++++++++++ gcc/testsuite/ChangeLog | 6 ++++++ 3 files changed, 21 insertions(+), 1 deletion(-) diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP index b56ada5674a..eaf59824aca 100644 --- a/gcc/DATESTAMP +++ b/gcc/DATESTAMP @@ -1 +1 @@ -20220911 +20220912 diff --git a/gcc/analyzer/ChangeLog b/gcc/analyzer/ChangeLog index 0e3cc72aa6f..ea6d5eeff3e 100644 --- a/gcc/analyzer/ChangeLog +++ b/gcc/analyzer/ChangeLog @@ -1,3 +1,17 @@ +2022-09-11 Tim Lange <mail@tim-lange.me> + + PR analyzer/106845 + * region-model.cc (region_model::check_region_bounds): + Bail out if 0 bytes were accessed. + * store.cc (byte_range::dump_to_pp): + Add special case for empty ranges. + (byte_range::exceeds_p): Restrict to non-empty ranges. + (byte_range::falls_short_of_p): Restrict to non-empty ranges. + * store.h (bit_range::empty_p): New function. + (bit_range::get_last_byte_offset): Restrict to non-empty ranges. + (byte_range::empty_p): New function. + (byte_range::get_last_byte_offset): Restrict to non-empty ranges. + 2022-09-09 David Malcolm <dmalcolm@redhat.com> * analyzer.opt (Wanalyzer-exposure-through-uninit-copy): New. diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog index ffe0c631778..dd4950eaf9e 100644 --- a/gcc/testsuite/ChangeLog +++ b/gcc/testsuite/ChangeLog @@ -1,3 +1,9 @@ +2022-09-11 Tim Lange <mail@tim-lange.me> + + PR analyzer/106845 + * gcc.dg/analyzer/out-of-bounds-zero.c: New test. + * gcc.dg/analyzer/pr106845.c: New test. + 2022-09-10 Takayuki 'January June' Suwa <jjsuwa_sys3175@yahoo.co.jp> * gcc.target/xtensa/constsynth_3insns.c (test_4):
reply other threads:[~2022-09-12 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=20220912001841.B7C7D3858C83@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).