Displaying 3 results from an estimated 3 matches for "fastdemagler".
Did you mean:
fastdemangler
2017 Jun 22
3
RFC: Cleaning up the Itanium demangler
On June 22, 2017 at 5:51:39 AM, Pavel Labath (labath at google.com) wrote:
I don't have any concrete feedback, but:
- +1 for removing the "FastDemagler"
- If you already construct an AST as a part of your demangling
process, would it be possible to export that AST for external
consumption somehow? Right now in lldb we sometimes need to parse the
demangled name (to get the "basename" of a function for example), and
the code for doin...
2017 Jun 22
2
[lldb-dev] RFC: Cleaning up the Itanium demangler
...2017 at 15:21, Erik Pilkington <erik.pilkington at gmail.com> wrote:
>>
>>
>>
>> On June 22, 2017 at 5:51:39 AM, Pavel Labath (labath at google.com) wrote:
>>
>> I don't have any concrete feedback, but:
>>
>> - +1 for removing the "FastDemagler"
>>
>> - If you already construct an AST as a part of your demangling
>> process, would it be possible to export that AST for external
>> consumption somehow? Right now in lldb we sometimes need to parse the
>> demangled name (to get the "basename" of a...
2017 Jun 22
3
RFC: Cleaning up the Itanium demangler
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)