similar to: RFC: Improving the performance of ItaniumDemangle

well, top-of-branch lldb uses this code, that's how I found it. Do you mean libc++'s demangler? FYI when I said 14+% (and now it's 17%), I mean the overall performance of starting lldb, not just the demangler itself. It's probably several times faster now with this change (https://reviews.llvm.org/D32500) On Tue, Apr 25, 2017 at 12:19 PM, Vedant Kumar <vsk at apple.com>

On Tue, Apr 25, 2017 at 8:36 PM, Vedant Kumar via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > > On Apr 25, 2017, at 12:24 PM, Scott Smith <scott.smith at purestorage.com> > wrote: > > > > well, top-of-branch lldb uses this code, that's how I found it. Do you > mean libc++'s demangler? > > Thanks for explaining, this is the first time

On Tue, Apr 25, 2017 at 1:37 PM, Asiri Rathnayake < asiri.rathnayake at gmail.com> wrote: > > > On Tue, Apr 25, 2017 at 8:36 PM, Vedant Kumar via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> >> > On Apr 25, 2017, at 12:24 PM, Scott Smith <scott.smith at purestorage.com> >> wrote: >> > >> > well, top-of-branch lldb

This is Greg's area, he'll be able to answer in detail how the name chopper gets used. IIRC it chops demangled names, so it is indirectly a client of the demangler, but it doesn't use the demangler to do this directly. Name lookup is done by finding all the base name matches, then comparing the context. We don't do a very good job of doing fuzzy full name matches - for instance

Hello all, The itanium demangler in libcxxabi (and also, llvm/lib/Demangle) is really slow. This is largely because the textual representation of the symbol that is being demangled is held in a std::string, and manipulations done during parsing are done on that string. The demangler is always concatenating strings and inserting into the middle of strings, which is terrible. The fact that the

On Sun, Mar 4, 2018 at 12:33 AM, John McCall <rjmccall at apple.com> wrote: > On Mar 3, 2018, at 11:30 PM, Daniel Berlin via cfe-dev < > cfe-dev at lists.llvm.org> wrote: > > To explain to others who didn't follow that thread: > > GDB currently does something amazingly stupid (and has since i wrote it) > to find the RTTI type. There were no other good options

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)

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

On Sun, 4 Mar 2018 at 20:33, John McCall via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > Seems like a reasonable project! Maybe we can get a SoC student to make a > standalone C++ demangler library with a tree API (an unstable one should be > fine), and debuggers can just use that instead of relying on the OS's > cxa_demangle. (I'm really not sure why

> On Mar 4, 2018, at 10:20 AM, Daniel Berlin <dberlin at dberlin.org> wrote: > > > > On Sun, Mar 4, 2018 at 12:33 AM, John McCall <rjmccall at apple.com <mailto:rjmccall at apple.com>> wrote: >> On Mar 3, 2018, at 11:30 PM, Daniel Berlin via cfe-dev <cfe-dev at lists.llvm.org <mailto:cfe-dev at lists.llvm.org>> wrote: >> >> To

> On Dec 15, 2016, at 6:18 AM, Dave Bozier via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hi all, > > > We’re hoping to replace the demangler in some of our tools to use the LLVM demangler. We’d like to enhance it with missing functionality (legal names that it cannot demangle) and provide a set of tests that we use with the demangler that we currently use. >

On Thu, May 5, 2016 at 10:58 AM, Duncan P. N. Exon Smith via llvm-dev < llvm-dev at lists.llvm.org> wrote: > +Kate > > We already have two demangler implementations (LLDB and libcxxabi). I'd > rather not have three. Have you looked at the LLDB one? I think Kate has > some patches she hasn't had a chance to commit yet that add functionality. > I heard something

> On May 5, 2016, at 11:50 AM, Duncan P. N. Exon Smith <dexonsmith at apple.com> wrote: > >> On 2016-May-05, at 11:14, David Majnemer <david.majnemer at gmail.com> wrote: >> >> On Thu, May 5, 2016 at 10:58 AM, Duncan P. N. Exon Smith via llvm-dev <llvm-dev at lists.llvm.org> wrote: >>> +Kate >>> >>> We already have two

Hi, I'm trying to run some old delphi application, which uses BDE to connect to an access mdb file. The application displays an error, that it couldn't open the database. I can run BDEADMIN and I see that database aliases are configured propoerly. I did some winedebugg'ing and noticed following mesassages .... ... warn:gdi:GDI_GetObjPtr Invalid handle (nil) warn:gdi:GDI_GetObjPtr

On Feb 26, 2:18 pm, Ralf Schneider <li... at gestaltgeber.com> wrote: > Hello, > > 2009/2/26 Talin <viri... at gmail.com> > > > The IR-level intrinsics themselves don't much help you *write* a GC, so > > much as to integrate one with LLVM. What is provided is essentially a > > mechanism for walking the stack, and a means to insert read/write > >

On 2009-02-26 18:22, Gabor Greif wrote: > On Feb 26, 2:18 pm, Ralf Schneider <li... at gestaltgeber.com> wrote: > >> Hello, >> >> 2009/2/26 Talin <viri... at gmail.com> >> >> >>> The IR-level intrinsics themselves don't much help you *write* a GC, so >>> much as to integrate one with LLVM. What is provided is essentially

Hello, I have been asked to come up with a strategy for centralized patch management of our linux servers. Today, this is only centos and rhel. What is everyone else doing in this arena? Thanks!

Hi, I really did my best to understand how I can help improving Wine, but I did not succed. Well, everything started when I installed a win application on my Debian 3.1, Wine 2004.07.16 deb (clean install, no dlls). The application is ALOHA (http://www.epa.gov/ceppo/cameo/aloha.htm) It's a free application from US-Environment Protection Agency used for chemical emergency planning (I am an

When I installed Arena 12 cpr 9 with a student license. I saw the error message RsiTPInfo030000.dll RSIXML06000.dll were missing. I installed on windows 7 to compare and had the same error. I tried re-installing/repair, without improvement. I extracted these two files from the data.cab file. Arena works fine now. I tried to inform rockwell automation, but they have no support for students. I

Hi, I tried to run MS Visio in wine, and it breaks while loading the first file or template. It says Fehlernr. 1 ist bei der '???'-Operation aufgetreten. Unerwartetes Dateiende. which translates into Fault 1: Unexpected EOF Going throug the debug output, I noticed file accesses for warn:file:FILE_DoOpenFile 'd:\visio\system\filter32\emigs9.flt' not found or sharing