search for: _z3fooiiiiiii

...tion, say getItaniumDemangledBasename(), which could just parse and query the AST for the base name (the AST already has an way of doing this). This would allow the demangler to bail out if it knows that the rest of the input string isn’t relevant, i.e., we could bail out after parsing the ‘foo’ in _Z3fooiiiiiii. That, and not having to print out the AST should make parsing the base name significantly faster on top of this. Do you have any other use case for the AST outside of base names? It still would be possible to export it from ItaniumDemangle. On 22 June 2017 at 02:03, Erik Pilkington via llvm-dev...

...e(), which could >> just parse and query the AST for the base name (the AST already has an way >> of doing this). This would allow the demangler to bail out if it knows that >> the rest of the input string isn’t relevant, i.e., we could bail out after >> parsing the ‘foo’ in _Z3fooiiiiiii. That, and not having to print out the >> AST should make parsing the base name significantly faster on top of this. >> >> Do you have any other use case for the AST outside of base names? It still >> would be possible to export it from ItaniumDemangle. >> > >...

On 6/21/17 5:42 PM, Rui Ueyama wrote: > I'm very interested in your work because I've just started writing a > demangler for the Microsoft mangling scheme. What I found in the > current Itanium demangler is the same as you -- it looks like it > allocates too much memory during parsing and concatenates std::strings > too often. I could see there's a (probably big)