From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
 id 841713858C3A; Wed, 20 Oct 2021 06:22:11 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 841713858C3A
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
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: demangler
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hasse.christoph at cern dot ch
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status
 bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-102851-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2021 06:22:11 -0000

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D102851

            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:=20
_ZZNK5Gaudi10Functional7details16MultiTransformerIFSt5tupleIJSt6vectorIN4LH=
Cb13VPFullClusterESaIS6_EESt5arrayIjLm53EEEERK12EventContextRKNS5_8RawEvent=
ERK4DeVPENS0_6Traits4use_IJNS5_7DetDesc21useConditionHandleForIJSI_EEENSM_1=
1BaseClass_tINSO_23ConditionAccessorHolderI10FixTESPathINS_9AlgorithmEEEEEE=
EEELb0EE7executeESE_ENKUlDpRT_E_clIJK21DataObjectWriteHandleIS8_S8_EKS15_IS=
A_SA_EEEEDaS12_

`llvm-cxxfilt` gives:=20
auto
Gaudi::Functional::details::MultiTransformer<std::tuple<std::vector<LHCb::V=
PFullCluster,
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::ConditionAccessorHold=
er<FixTESPath<Gaudi::Algorithm>
> > >, false>::execute(EventContext const&)
const::'lambda'(auto&...)::operator()<DataObjectWriteHandle<std::vector<LHC=
b::VPFullCluster,
std::allocator<LHCb::VPFullCluster> >, std::vector<LHCb::VPFullCluster,
std::allocator<LHCb::VPFullCluster> > > const,
DataObjectWriteHandle<std::array<unsigned int, 53ul>, std::array<unsigned i=
nt,
53ul> > const>(auto&...) const=