public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "arsenic at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/101980] [12 regressions] many test case failures after r12-3002
Date: Wed, 25 Aug 2021 08:32:57 +0000 [thread overview]
Message-ID: <bug-101980-4-thvZQfM3e2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101980-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101980
--- Comment #5 from Ankur Saini <arsenic at gcc dot gnu.org> ---
(In reply to Hans-Peter Nilsson from comment #4)
> (In reply to Ankur Saini from comment #3)
> > Fixed after the following commits:
> > e92d0ff6b5e6d4b95c04fc3e326d40efeb136086
> > 537878152ded8b7d271333b803b36c27a9aea8d2
>
> g++.dg/analyzer/pr96641.C, a regression introduced by this commit (or
> unlikely, another commit in the series 640df4ef815a..f0fca213bc52), remains
> to be fixed.
> It seems to fail everywhere:
>
> s390x-ibm-linux-gnu
> https://gcc.gnu.org/pipermail/gcc-testresults/2021-August/716425.html
>
> x86_64-pc-linux-gnu 3c496e92d795a8fe5c527e3c5b5a6606669ae50d
> https://gcc.gnu.org/pipermail/gcc-testresults/2021-August/716406.html
>
> powerpc64-unknown-linux-gnu 6d692ef43b2b3368c92c3fb757c7884fc94ee627
> https://gcc.gnu.org/pipermail/gcc-testresults/2021-August/716400.html
>
> powerpc64le-unknown-linux-gnu 3c496e92d795a8fe5c527e3c5b5a6606669ae50d
> https://gcc.gnu.org/pipermail/gcc-testresults/2021-August/716428.html
>
> i686-pc-linux-gnu 6e5401e87d02919b0594e04f828892deef956407
> https://gcc.gnu.org/pipermail/gcc-testresults/2021-August/716332.html
>
> powerpc-ibm-aix7.2.3.0 0312e263b6afa5b545c2d3b7c7ac5295ecaa7fa8
> https://gcc.gnu.org/pipermail/gcc-testresults/2021-August/716308.html
>
> m68k-unknown-linux-gnu 192d4edd15c
> https://gcc.gnu.org/pipermail/gcc-testresults/2021-August/716297.html
>
> For cris-elf, I see this in g++.log:
> /X/gcc/testsuite/g++.dg/analyzer/pr96641.C:8:3: warning: analysis bailed out
> early (91 'after-snode' enodes; 228 enodes) [-Wanalyzer-too-complex]
Thanks for pointing this out.
This is due to the fact that analyzer doesn't have a maximum recursion limit
when analysing dynamically discovered calls ( vfunc calls or calls that happen
via a function pointer ).
I have sent a patch on the patches list which should fix this problem.
- - -
Patch : https://gcc.gnu.org/pipermail/gcc-patches/2021-August/578091.html
next prev parent reply other threads:[~2021-08-25 8:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 14:50 [Bug analyzer/101980] New: " seurer at gcc dot gnu.org
2021-08-19 15:06 ` [Bug analyzer/101980] " dmalcolm at gcc dot gnu.org
2021-08-20 8:28 ` rguenth at gcc dot gnu.org
2021-08-21 5:04 ` cvs-commit at gcc dot gnu.org
2021-08-23 14:29 ` arsenic at gcc dot gnu.org
2021-08-24 23:07 ` hp at gcc dot gnu.org
2021-08-25 8:32 ` arsenic at gcc dot gnu.org [this message]
2021-08-25 13:30 ` cvs-commit at gcc dot gnu.org
2021-08-25 13:33 ` arsenic at gcc dot gnu.org
2021-08-25 21:08 ` hp 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-101980-4-thvZQfM3e2@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).