public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "seurer at linux dot vnet.ibm.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/94853] New: [10 regression] excess errors in gfortran.dg/analyzer/pr93993.f90 since r10-8012
Date: Wed, 29 Apr 2020 17:03:08 +0000 [thread overview]
Message-ID: <bug-94853-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94853
Bug ID: 94853
Summary: [10 regression] excess errors in
gfortran.dg/analyzer/pr93993.f90 since r10-8012
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: testsuite
Assignee: unassigned at gcc dot gnu.org
Reporter: seurer at linux dot vnet.ibm.com
Target Milestone: ---
commit g:78b9783774bfd3540f38f5b1e3c7fc9f719653d7, r10-8012
spawn -ignore SIGHUP
/home3/seurer/gcc/git/build/gcc-test2/gcc/testsuite/gfortran/../../gfortran
-B/home3/seurer/gcc/git/build/gcc-test2/gcc/testsuite/gfortran/../../
-B/home3/seurer/gcc/git/build/gcc-test2/powerpc64le-unknown-linux-gnu/./libgfortran/
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/gfortran.dg/analyzer/pr93993.f90
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -fdiagnostics-urls=never -O -fanalyzer
-fdiagnostics-path-format=separate-events -Wanalyzer-too-complex
-fanalyzer-call-summaries -S -o pr93993.s
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/gfortran.dg/analyzer/pr93993.f90:21:0:
Warning: leak of 'tm' [CWE-401] [-Wanalyzer-malloc-leak]
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/gfortran.dg/analyzer/pr93993.f90:26:0:
note: (1) entry to 'main'
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/gfortran.dg/analyzer/pr93993.f90:26:0:
note: (2) calling 'a5' from 'main'
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/gfortran.dg/analyzer/pr93993.f90:25:0:
note: (3) entry to 'a5'
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/gfortran.dg/analyzer/pr93993.f90:32:0:
note: (4) calling 'hv' from 'a5'
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/gfortran.dg/analyzer/pr93993.f90:15:0:
note: (5) entry to 'hv'
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/gfortran.dg/analyzer/pr93993.f90:19:0:
note: (6) following 'false' branch...
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/gfortran.dg/analyzer/pr93993.f90:19:0:
note: (7) ...to here
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/gfortran.dg/analyzer/pr93993.f90:19:0:
note: (8) following 'false' branch...
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/gfortran.dg/analyzer/pr93993.f90:19:0:
note: (9) ...to here
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/gfortran.dg/analyzer/pr93993.f90:21:0:
note: (10) 'tm' leaks here
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/gfortran.dg/analyzer/pr93993.f90:33:0:
Warning: leak of '(struct Pdtet_8 *) qb' [CWE-401] [-Wanalyzer-malloc-leak]
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/gfortran.dg/analyzer/pr93993.f90:26:0:
note: (1) entry to 'main'
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/gfortran.dg/analyzer/pr93993.f90:26:0:
note: (2) calling 'a5' from 'main'
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/gfortran.dg/analyzer/pr93993.f90:25:0:
note: (3) entry to 'a5'
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/gfortran.dg/analyzer/pr93993.f90:32:0:
note: (4) calling 'hv' from 'a5'
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/gfortran.dg/analyzer/pr93993.f90:15:0:
note: (5) entry to 'hv'
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/gfortran.dg/analyzer/pr93993.f90:19:0:
note: (6) following 'false' branch...
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/gfortran.dg/analyzer/pr93993.f90:19:0:
note: (7) ...to here
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/gfortran.dg/analyzer/pr93993.f90:19:0:
note: (8) allocated here
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/gfortran.dg/analyzer/pr93993.f90:19:0:
note: (9) allocated here
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/gfortran.dg/analyzer/pr93993.f90:19:0:
note: (10) state of '(struct Pdtet_8 *) qb': 'start' -> 'nonnull' (origin:
NULL)
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/gfortran.dg/analyzer/pr93993.f90:19:0:
note: (11) following 'false' branch...
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/gfortran.dg/analyzer/pr93993.f90:19:0:
note: (12) ...to here
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/gfortran.dg/analyzer/pr93993.f90:19:0:
note: (13) state of '(struct Pdtet_8 *) qb': 'start' -> 'nonnull' (origin:
NULL)
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/gfortran.dg/analyzer/pr93993.f90:21:0:
note: (14) state of '(struct Pdtet_8 *) qb': 'start' -> 'nonnull' (origin:
NULL)
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/gfortran.dg/analyzer/pr93993.f90:32:0:
note: (15) returning to 'a5' from 'hv'
f951: note: (16) state of '(struct Pdtet_8 *) qb': 'start' -> 'nonnull'
(origin: NULL)
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/gfortran.dg/analyzer/pr93993.f90:33:0:
note: (17) state of '(struct Pdtet_8 *) qb': 'start' -> 'nonnull' (origin:
NULL)
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/gfortran.dg/analyzer/pr93993.f90:33:0:
note: (18) state of '(struct Pdtet_8 *) qb': 'start' -> 'nonnull' (origin:
NULL)
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/gfortran.dg/analyzer/pr93993.f90:33:0:
note: (19) '(struct Pdtet_8 *) qb' leaks here; was allocated at (9)
PASS: gfortran.dg/analyzer/pr93993.f90 -O (test for bogus messages, line
19)
PASS: gfortran.dg/analyzer/pr93993.f90 -O (test for warnings, line 33)
Executing on host:
/home3/seurer/gcc/git/build/gcc-test2/gcc/testsuite/gfortran/../../gfortran
-B/home3/seurer/gcc/git/build/gcc-test2/gcc/testsuite/gfortran/../../
-B/home3/seurer/gcc/git/build/gcc-test2/powerpc64le-unknown-linux-gnu/./libgfortran/
exceptions_enabled44136.c -fno-diagnostics-show-caret
-fno-diagnostics-show-line-numbers -fdiagnostics-color=never
-fdiagnostics-urls=never -S -o exceptions_enabled44136.s (timeout = 300)
spawn -ignore SIGHUP
/home3/seurer/gcc/git/build/gcc-test2/gcc/testsuite/gfortran/../../gfortran
-B/home3/seurer/gcc/git/build/gcc-test2/gcc/testsuite/gfortran/../../
-B/home3/seurer/gcc/git/build/gcc-test2/powerpc64le-unknown-linux-gnu/./libgfortran/
exceptions_enabled44136.c -fno-diagnostics-show-caret
-fno-diagnostics-show-line-numbers -fdiagnostics-color=never
-fdiagnostics-urls=never -S -o exceptions_enabled44136.s
exceptions_enabled44136.c: In function 'foo':
exceptions_enabled44136.c:4:7: error: 'throw' undeclared (first use in this
function)
exceptions_enabled44136.c:4:7: note: each undeclared identifier is reported
only once for each function it appears in
exceptions_enabled44136.c:4:12: error: expected ';' before numeric constant
compiler exited with status 1
FAIL: gfortran.dg/analyzer/pr93993.f90 -O (test for excess errors)
Excess errors:
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/gfortran.dg/analyzer/pr93993.f90:21:0:
Warning: leak of 'tm' [CWE-401] [-Wanalyzer-malloc-leak]
next reply other threads:[~2020-04-29 17:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 17:03 seurer at linux dot vnet.ibm.com [this message]
2020-04-29 17:19 ` [Bug testsuite/94853] " jakub at gcc dot gnu.org
2020-04-30 6:43 ` rguenth at gcc dot gnu.org
2020-05-01 15:19 ` [Bug testsuite/94853] [10/11 " ro at gcc dot gnu.org
2020-05-07 11:56 ` jakub at gcc dot gnu.org
2020-06-03 7:23 ` marxin at gcc dot gnu.org
2020-07-23 6:51 ` rguenth at gcc dot gnu.org
2021-01-14 8:40 ` rguenth at gcc dot gnu.org
2021-04-08 12:02 ` rguenth at gcc dot gnu.org
2021-05-04 12:31 ` [Bug testsuite/94853] [10/11/12 " rguenth at gcc dot gnu.org
2021-10-05 22:54 ` bergner at gcc dot gnu.org
2022-06-28 10:40 ` [Bug testsuite/94853] [10/11/12/13 " jakub at gcc dot gnu.org
2023-07-07 10:37 ` [Bug testsuite/94853] [11/12/13/14 " rguenth at gcc dot gnu.org
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=bug-94853-4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).