search for: ripopov

...7525328 1.6 % std::cout << "hello world!" 21552 22080 2.4 % IMO, not that big price for reliable dynamic type identification (Full disclosure: I need depend on this feature, since I'm writing Python pretty printers for GDB ) -Roman 2018-03-02 18:12 GMT-08:00 Roman Popov <ripopov at gmail.com>: > Mangled names can be long indeed, but pretty-printed types are also long. > I can evaluate effect on size on clang codebase itself. > > If you disable RTTI, than obviously you can't use it. So if RTTI is > disabled, we can disable mangled names in DWARF. Clan...

Mangled names can be long indeed, but pretty-printed types are also long. I can evaluate effect on size on clang codebase itself. If you disable RTTI, than obviously you can't use it. So if RTTI is disabled, we can disable mangled names in DWARF. Clang is compiled without standard C++ RTTI because it has it's own RTTI. In general, however, many libraries use standard RTTI. 2018-03-02

...t dberlin.org> wrote: > On Tue, Mar 6, 2018 at 9:22 AM, David Blaikie <dblaikie at gmail.com> wrote: > >> >> >> On Tue, Mar 6, 2018 at 8:39 AM Daniel Berlin <dberlin at dberlin.org> wrote: >> >>> On Mon, Mar 5, 2018 at 11:55 PM, Roman Popov <ripopov at gmail.com> wrote: >>> >>>> I don't understand how extra vtable ref DIE will help in case on >>>> non-polymorphic classes. If you remove virtual destructor from example, >>>> vtable won't be generated for class, but DWARF will still have inc...

On Tue, Mar 6, 2018 at 9:22 AM, David Blaikie <dblaikie at gmail.com> wrote: > > > On Tue, Mar 6, 2018 at 8:39 AM Daniel Berlin <dberlin at dberlin.org> wrote: > >> On Mon, Mar 5, 2018 at 11:55 PM, Roman Popov <ripopov at gmail.com> wrote: >> >>> I don't understand how extra vtable ref DIE will help in case on >>> non-polymorphic classes. If you remove virtual destructor from example, >>> vtable won't be generated for class, but DWARF will still have incorrect >>&...

...org> wrote: > > > On Tue, Mar 6, 2018 at 9:22 AM, David Blaikie <dblaikie at gmail.com> wrote: > >> >> >> On Tue, Mar 6, 2018 at 8:39 AM Daniel Berlin <dberlin at dberlin.org> wrote: >> >>> On Mon, Mar 5, 2018 at 11:55 PM, Roman Popov <ripopov at gmail.com> wrote: >>> >>>> I don't understand how extra vtable ref DIE will help in case on >>>> non-polymorphic classes. If you remove virtual destructor from example, >>>> vtable won't be generated for class, but DWARF will still have inc...

On Tue, Mar 6, 2018 at 9:20 AM, Roman Popov <ripopov at gmail.com> wrote: > I wonder if abi::__cxa_demangle guarantees unambigous names? >>> >> >> No, it does not. >> > > Interesting. Can you give an example of type where it fails? > I can't construct one out of thin air, but i believe someone cited on...

..., Mar 6, 2018 at 9:22 AM, David Blaikie <dblaikie at gmail.com> wrote: >> >>> >>> >>> On Tue, Mar 6, 2018 at 8:39 AM Daniel Berlin <dberlin at dberlin.org> >>> wrote: >>> >>>> On Mon, Mar 5, 2018 at 11:55 PM, Roman Popov <ripopov at gmail.com> wrote: >>>> >>>>> I don't understand how extra vtable ref DIE will help in case on >>>>> non-polymorphic classes. If you remove virtual destructor from example, >>>>> vtable won't be generated for class, but DWARF wil...

On Tue, Mar 6, 2018 at 8:39 AM Daniel Berlin <dberlin at dberlin.org> wrote: > On Mon, Mar 5, 2018 at 11:55 PM, Roman Popov <ripopov at gmail.com> wrote: > >> I don't understand how extra vtable ref DIE will help in case on >> non-polymorphic classes. If you remove virtual destructor from example, >> vtable won't be generated for class, but DWARF will still have incorrect >> ambiguous names...

On Tue, Mar 6, 2018 at 9:49 AM Daniel Berlin <dberlin at dberlin.org> wrote: > On Tue, Mar 6, 2018 at 9:20 AM, Roman Popov <ripopov at gmail.com> wrote: > >> I wonder if abi::__cxa_demangle guarantees unambigous names? >>>> >>> >>> No, it does not. >>> >> >> Interesting. Can you give an example of type where it fails? >> > > I can't construct one ou...

...in debugger, and then load it in Clang to do some source-to-source transformations. This is what I've planned for my hardware construction library. -Roman 2018-03-06 8:39 GMT-08:00 Daniel Berlin <dberlin at dberlin.org>: > > > On Mon, Mar 5, 2018 at 11:55 PM, Roman Popov <ripopov at gmail.com> wrote: > >> I don't understand how extra vtable ref DIE will help in case on >> non-polymorphic classes. If you remove virtual destructor from example, >> vtable won't be generated for class, but DWARF will still have incorrect >> ambiguous names...

On Mon, Mar 5, 2018 at 11:55 PM, Roman Popov <ripopov at gmail.com> wrote: > I don't understand how extra vtable ref DIE will help in case on > non-polymorphic classes. If you remove virtual destructor from example, > vtable won't be generated for class, but DWARF will still have incorrect > ambiguous names for types. > 1. C...

I don't understand how extra vtable ref DIE will help in case on non-polymorphic classes. If you remove virtual destructor from example, vtable won't be generated for class, but DWARF will still have incorrect ambiguous names for types. It will become a problem when you need to use debuginfo as a C++ runtime reflection (I've already seen this in a couple of projects). Or when you need