[Bug c++/70909] Libiberty Demangler segfaults (4)

[trippels at gcc dot gnu.org]

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

--- Comment #33 from Markus Trippelsdorf <trippels at gcc dot gnu.org> ---
(In reply to Mark Wielaard from comment #32)
> - PR70517
> _ZSt4moveIRZN11tconcurrent6futureIvE4thenIZ5awaitIS2_EDaOT_EUlRKS6_E_EENS1_IN
> St5decayIDTclfp_defpTEEE4typeEEES7_EUlvE_EONSt16remove_referenceIS6_E4typeES7
> _

This one demangles just fine with Nathan's patch.

> 
> - PR68700
> _ZN8futurizeI13frozen_schemaE5applyIRZN7seastar7shardedIN7service13storage_pr
> oxyEE9invoke_onIZZNS6_22init_messaging_serviceEvENKUljN5utils4UUIDEE8_clEjSA_
> EUlOT_E_6futureIJS0_EEEET0_jSD_EUlvE_JEEESG_SD_DpOT0_
> This looks like it comes from a real compiler, dunno what it should demangle
> to.

This one, too. 

> - PR61460
> _ZNK6clover6detail11basic_rangeINS_13adaptor_rangeINS_9addressesEINS2_IRFRNS_
> 5eventEP9_cl_eventEINS_14iterator_rangeIPKS7_EEEEEEEENS0_16iterator_adaptorIS
> 3_INSG_IS9_ISC_EEEEEESI_EcvT_ISt6vectorIPS4_SaISN_EEvEEv
> The referenced GDB bug claims this comes from clover's libOpenCL in Mesa,
> but doesn't state which compiler.

None of the three demanglers could handle this one.