public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hasse.christoph at cern dot ch" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug demangler/102851] New: Failure to demangle c++ symbol
Date: Wed, 20 Oct 2021 06:22:11 +0000 [thread overview]
Message-ID: <bug-102851-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102851
Bug ID: 102851
Summary: Failure to demangle c++ symbol
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: demangler
Assignee: unassigned at gcc dot gnu.org
Reporter: hasse.christoph at cern dot ch
Target Milestone: ---
As far as I now understand c++filt uses libiberty to demangle which is part of
GCC, so filing this bug here.
Originally observed in perf, but reproduced with c++filt Version 2.36.1
Symbol:
_ZZNK5Gaudi10Functional7details16MultiTransformerIFSt5tupleIJSt6vectorIN4LHCb13VPFullClusterESaIS6_EESt5arrayIjLm53EEEERK12EventContextRKNS5_8RawEventERK4DeVPENS0_6Traits4use_IJNS5_7DetDesc21useConditionHandleForIJSI_EEENSM_11BaseClass_tINSO_23ConditionAccessorHolderI10FixTESPathINS_9AlgorithmEEEEEEEEELb0EE7executeESE_ENKUlDpRT_E_clIJK21DataObjectWriteHandleIS8_S8_EKS15_ISA_SA_EEEEDaS12_
`llvm-cxxfilt` gives:
auto
Gaudi::Functional::details::MultiTransformer<std::tuple<std::vector<LHCb::VPFullCluster,
std::allocator<LHCb::VPFullCluster> >, std::array<unsigned int, 53ul> >
(EventContext const&, LHCb::RawEvent const&, DeVP const&),
Gaudi::Functional::Traits::use_<LHCb::DetDesc::useConditionHandleFor<DeVP>,
Gaudi::Functional::Traits::BaseClass_t<LHCb::DetDesc::ConditionAccessorHolder<FixTESPath<Gaudi::Algorithm>
> > >, false>::execute(EventContext const&)
const::'lambda'(auto&...)::operator()<DataObjectWriteHandle<std::vector<LHCb::VPFullCluster,
std::allocator<LHCb::VPFullCluster> >, std::vector<LHCb::VPFullCluster,
std::allocator<LHCb::VPFullCluster> > > const,
DataObjectWriteHandle<std::array<unsigned int, 53ul>, std::array<unsigned int,
53ul> > const>(auto&...) const
next reply other threads:[~2021-10-20 6:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 6:22 hasse.christoph at cern dot ch [this message]
2021-10-24 6:14 ` [Bug demangler/102851] " pinskia at gcc dot gnu.org
2021-10-25 14:34 ` hasse.christoph at cern dot ch
2022-10-07 16:56 ` ppalka 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-102851-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).