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-3096] analyzer: add regression test for PR 107158
Date: Wed,  5 Oct 2022 18:08:07 +0000 (GMT)	[thread overview]
Message-ID: <20221005180807.7E55C3858C54@sourceware.org> (raw)

https://gcc.gnu.org/g:ef878564140cbcf23f479da88e07e5a996cec6bb

commit r13-3096-gef878564140cbcf23f479da88e07e5a996cec6bb
Author: David Malcolm <dmalcolm@redhat.com>
Date:   Wed Oct 5 14:07:47 2022 -0400

    analyzer: add regression test for PR 107158
    
    PR analyzer/107158 reports an ICE when using
      -fanalyzer -fanalyzer-call-summaries
    on a particular source file.
    
    It turns out I just fixed this ICE in r13-3094-g6832c95c0e1a58.
    
    This followup patch adds a somewhat reduced reproducer as a regression
    test.  Unfortunately, although the ICE is fixed, there are two false
    positives from -Wanalyzer-malloc-leak on the test case, so I'm going to
    use PR analyzer/107158 for tracking those false positives.
    
    gcc/testsuite/ChangeLog:
            PR analyzer/107158
            * gcc.dg/analyzer/call-summaries-pr107158.c: New test.
    
    Signed-off-by: David Malcolm <dmalcolm@redhat.com>

Diff:
---
 .../gcc.dg/analyzer/call-summaries-pr107158.c      | 83 ++++++++++++++++++++++
 1 file changed, 83 insertions(+)

diff --git a/gcc/testsuite/gcc.dg/analyzer/call-summaries-pr107158.c b/gcc/testsuite/gcc.dg/analyzer/call-summaries-pr107158.c
new file mode 100644
index 00000000000..54f442f0ad4
--- /dev/null
+++ b/gcc/testsuite/gcc.dg/analyzer/call-summaries-pr107158.c
@@ -0,0 +1,83 @@
+/* { dg-additional-options "-fanalyzer-call-summaries" } */
+
+typedef __SIZE_TYPE__ size_t;
+enum { _ISspace = ((5) < 8 ? ((1 << (5)) << 8) : ((1 << (5)) >> 8)) };
+extern const unsigned short int **__ctype_b_loc(void)
+  __attribute__((__nothrow__, __leaf__, __const__));
+extern void *malloc(size_t __size)
+  __attribute__((__nothrow__, __leaf__, __malloc__, __alloc_size__(1)));
+extern char *strcpy(char *__restrict __dest, const char *__restrict __src)
+  __attribute__((__nothrow__, __leaf__, __nonnull__(1, 2)));
+extern size_t strlen(const char *__s)
+  __attribute__((__nothrow__, __leaf__, __pure__, __nonnull__(1)));
+
+struct mydata {
+  struct mydata *link;
+  char *name;
+  char *type;
+};
+
+static struct mydata *all_data;
+static int line_no;
+
+__attribute__((__noreturn__)) void failed(const char *message);
+
+static char *string_dup(const char *string) {
+  char *buf;
+
+  if ((buf = malloc(strlen(string) + 1)) == ((void *)0))
+    failed("malloc() failed");
+
+  return strcpy(buf, string);
+}
+
+static void store_data(const char *name, const char *type) {
+  struct mydata *p, *q;
+
+  if ((p = (struct mydata *)malloc(sizeof(struct mydata))) == ((void *)0))
+    failed("malloc() failed");
+
+  p->link = ((void *)0);
+  p->name = string_dup(name);
+  p->type = string_dup(type);
+
+  if ((q = all_data) == ((void *)0))
+    all_data = p;
+  else {
+    while (q->link != ((void *)0))
+      q = q->link;
+    q->link = p;
+  }
+}
+
+static void parse_tbl(char *buffer) {
+  char *s = buffer;
+  char *t = s + strlen(s);
+
+  do {
+    t--;
+    if (((*__ctype_b_loc())[(int)(((int)*t))] & (unsigned short int)_ISspace))
+      *t = '\0';
+    else
+      break;
+  } while (t > s);
+  while (((*__ctype_b_loc())[(int)(((int)*s))] & (unsigned short int)_ISspace))
+    s++;
+  buffer = s;
+
+  line_no++;
+  if (*buffer != ';' && *buffer != '\0') {
+    if (*buffer == '#') {
+      store_data(buffer, ""); /* { dg-bogus "leak" "PR analyzer/107158" { xfail *-*-* } } */
+    } else {
+
+      while (*s && !((*__ctype_b_loc())[(int)(((int)*s))] &
+                     (unsigned short int)_ISspace))
+        s++;
+      while (
+          ((*__ctype_b_loc())[(int)(((int)*s))] & (unsigned short int)_ISspace))
+        *s++ = '\0';
+      store_data(buffer, s); /* { dg-bogus "leak" "PR analyzer/107158" { xfail *-*-* } } */
+    }
+  }
+}

                 reply	other threads:[~2022-10-05 18:08 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=20221005180807.7E55C3858C54@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: link
Be 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).