public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Tim Lange <tlange@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-2037] testsuite: Disable out-of-bounds checker in analyzer/torture/pr93451.c Date: Sat, 13 Aug 2022 12:05:48 +0000 (GMT) [thread overview] Message-ID: <20220813120548.433123858C54@sourceware.org> (raw) https://gcc.gnu.org/g:21d52d11df82e55abfdde3c5c49fbcc103d83861 commit r13-2037-g21d52d11df82e55abfdde3c5c49fbcc103d83861 Author: Tim Lange <mail@tim-lange.me> Date: Sat Aug 13 13:31:45 2022 +0200 testsuite: Disable out-of-bounds checker in analyzer/torture/pr93451.c This patch disables Wanalyzer-out-of-bounds for analyzer/torture/pr93451.c and makes the test case pass when compiled with -m32. The emitted warning is a true positive but only occurs if sizeof (long int) is less than sizeof (double). I've already discussed a similar case with Dave in the context of pr96764.c and we came to the conclusion that we just disable the checker in such cases. Committed under the "obvious fix" rule. gcc/testsuite/ChangeLog: * gcc.dg/analyzer/torture/pr93451.c: Disable Wanalyzer-out-of-bounds. Diff: --- gcc/testsuite/gcc.dg/analyzer/torture/pr93451.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/gcc/testsuite/gcc.dg/analyzer/torture/pr93451.c b/gcc/testsuite/gcc.dg/analyzer/torture/pr93451.c index 5908bc4b69f..daac745d504 100644 --- a/gcc/testsuite/gcc.dg/analyzer/torture/pr93451.c +++ b/gcc/testsuite/gcc.dg/analyzer/torture/pr93451.c @@ -1,3 +1,5 @@ +/* { dg-additional-options "-Wno-analyzer-out-of-bounds" } */ + void mt (double);
reply other threads:[~2022-08-13 12:05 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=20220813120548.433123858C54@sourceware.org \ --to=tlange@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).