From: Gerald Pfeifer <gerald@pfeifer.com>
To: David Malcolm <dmalcolm@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [committed] analyzer: support "bifurcation"; reimplement realloc [PR99260]
Date: Wed, 8 Sep 2021 21:02:36 +0200 (CEST) [thread overview]
Message-ID: <e2606845-26df-85d7-5d7f-17ba4ddd70@pfeifer.com> (raw)
In-Reply-To: <3d60ed25-da7c-3d1f-6a6e-314aa9651726@pfeifer.com>
On Fri, 3 Sep 2021, Gerald Pfeifer wrote:
> On Mon, 30 Aug 2021, David Malcolm via Gcc-patches wrote:
>> gcc/analyzer/ChangeLog:
>> PR analyzer/99260
>> * analyzer.h (class custom_edge_info): New class, adapted from
>> exploded_edge::custom_info_t. Make member functions const.
>> Make update_model return bool, converting edge param from
>> reference to a pointer, and adding a ctxt param.
>> (class path_context): New class.
>> * call-info.cc: New file.
>> * call-info.h: New file.
>> * engine.cc: Include "analyzer/call-info.h" and <memory>.
> I believe it is this change that is causing bootstrap to fail with
>
> In file included from /scratch/tmp/gerald/GCC-HEAD/gcc/analyzer/engine.cc:69:
> In file included from /usr/include/c++/v1/memory:653:
> /usr/include/c++/v1/typeinfo:346:5: error: no member named 'fancy_abort'
> in name space 'std::__1'; did you mean simply 'fancy_abort'?
> _VSTD::abort();
> ^~~~~~~
> /usr/include/c++/v1/__config:782:15: note: expanded from macro '_VSTD'
> #define _VSTD std::_LIBCPP_ABI_NAMESPACE
I'm now 99% certain this patch is the trigger and also filed a bug
report:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102242
Good news is that I have prototype patch in testing, so if you have not
started yet I suggest to wait and I should have an updated by tomorrow
morning.
Gerald
prev parent reply other threads:[~2021-09-08 19:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 22:45 David Malcolm
2021-09-03 18:00 ` Gerald Pfeifer
2021-09-08 19:02 ` Gerald Pfeifer [this message]
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=e2606845-26df-85d7-5d7f-17ba4ddd70@pfeifer.com \
--to=gerald@pfeifer.com \
--cc=dmalcolm@redhat.com \
--cc=gcc-patches@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).