public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: David Malcolm <dmalcolm@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-5389] analyzer: fix SARD-tc841-basic-00182-min.c test case [PR108507] Date: Thu, 26 Jan 2023 14:13:50 +0000 (GMT) [thread overview] Message-ID: <20230126141350.B19893858438@sourceware.org> (raw) https://gcc.gnu.org/g:f1eab269288ffa80ba924ddb4c4b36f8f781d613 commit r13-5389-gf1eab269288ffa80ba924ddb4c4b36f8f781d613 Author: David Malcolm <dmalcolm@redhat.com> Date: Thu Jan 26 09:12:21 2023 -0500 analyzer: fix SARD-tc841-basic-00182-min.c test case [PR108507] gcc/testsuite/ChangeLog: PR analyzer/108507 * gcc.dg/analyzer/SARD-tc841-basic-00182-min.c: Add -Wno-stringop-overflow. Signed-off-by: David Malcolm <dmalcolm@redhat.com> Diff: --- gcc/testsuite/gcc.dg/analyzer/SARD-tc841-basic-00182-min.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/gcc/testsuite/gcc.dg/analyzer/SARD-tc841-basic-00182-min.c b/gcc/testsuite/gcc.dg/analyzer/SARD-tc841-basic-00182-min.c index 577dce13f00..ed9ad317d19 100644 --- a/gcc/testsuite/gcc.dg/analyzer/SARD-tc841-basic-00182-min.c +++ b/gcc/testsuite/gcc.dg/analyzer/SARD-tc841-basic-00182-min.c @@ -4,6 +4,9 @@ Black, P. , Koo, H. and Irish, T. (2013), A Basic CWE-121 Buffer Overflow Effectiveness Test Suite, Proc. 6th Latin-American Symposium on Dependable Computing, Rio de Janeiro, -1, [online], https://tsapps.nist.gov/publication/get_pdf.cfm?pub_id=913117 (Accessed January 17, 2023) */ +/* The purpose of this testcase is to see if -fanalyzer can detect the bug. */ +/* { dg-additional-options "-Wno-stringop-overflow" } */ + /* Taxonomy Classification: 0000300602130000031110 */ /*
reply other threads:[~2023-01-26 14:13 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=20230126141350.B19893858438@sourceware.org \ --to=dmalcolm@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).