search for: unmangl

Hi, I am looking for a way to get unmangled subprogram names from a DWARFContext. The name I want is available in the attribute `DW_AT_name` [1], but as far as I can tell this is only returned as a fallback in `DWARFDebugInfoEntryMinimal::getSubroutineName` when the linkage name is not available [2]. If this is not currently possible, is...

...possible with the public API or am I mistaking? On Wed, May 7, 2014 at 12:13 AM, Eric Christopher <echristo at gmail.com>wrote: > On Tue, May 6, 2014 at 8:09 PM, Isaiah Norton <isaiah.norton at gmail.com> > wrote: > > Hi, > > > > I am looking for a way to get unmangled subprogram names from a > > DWARFContext. The name I want is available in the attribute `DW_AT_name` > > [1], but as far as I can tell this is only returned as a fallback in > > `DWARFDebugInfoEntryMinimal::getSubroutineName` when the linkage name is > not > > available...

...ARF structure because what we need is already stored there anyway. Thanks, Isaiah On Wed, May 7, 2014 at 12:24 PM, Alexey Samsonov <samsonov at google.com>wrote: > Yeah, public API of DebugInfo library is quite minimalistic. But I agree > with Eric - what is the use case for getting unmangled name from DIE? > > > On Tue, May 6, 2014 at 11:21 PM, Keno Fischer < > kfischer at college.harvard.edu> wrote: > >> That doesn't seem possible with the public API or am I mistaking? >> >> >> On Wed, May 7, 2014 at 12:13 AM, Eric Christopher <ech...

...> Isaiah > > > > > > On Wed, May 7, 2014 at 12:24 PM, Alexey Samsonov <samsonov at google.com> > > wrote: > >> > >> Yeah, public API of DebugInfo library is quite minimalistic. But I agree > >> with Eric - what is the use case for getting unmangled name from DIE? > >> > >> > >> On Tue, May 6, 2014 at 11:21 PM, Keno Fischer > >> <kfischer at college.harvard.edu> wrote: > >>> > >>> That doesn't seem possible with the public API or am I mistaking? > >>> > >...

...Wed, May 7, 2014 at 12:24 PM, Alexey Samsonov <samsonov at google.com> >>> > wrote: >>> >> >>> >> Yeah, public API of DebugInfo library is quite minimalistic. But I >>> agree >>> >> with Eric - what is the use case for getting unmangled name from DIE? >>> >> >>> >> >>> >> On Tue, May 6, 2014 at 11:21 PM, Keno Fischer >>> >> <kfischer at college.harvard.edu> wrote: >>> >>> >>> >>> That doesn't seem possible with the public AP...

...g. I > know linker diagnostics would benefit from a deeper understanding of the > name without having to parse C++ decls. > Somewhat off the cuff, but I think it would be nice if commandline object inspection tools could query for a particular symbol when the user specified it in the C++, unmangled form. Generally, it seems useful to unify the mangling and unmangling code if only so that we constantly round-trip test both halves and don't end up with divergences. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev...

When having a project that's partially bitcode and partially native code, should lld allow linking a native .o to a bitcode .o? specifically in my case, I've got an stdcall function in bitcode, called by native code, but it can't find the symbol (bitcode has it unmangled, native code with _ and @20)

On Jul 5, 2012, at 1:08 AM, Chandler Carruth <chandlerc at google.com> wrote: > In the same way that the core LLVM libraries have support routines for DWARF, I think that both mangling and demangling should be provided as well. How would LLVM provide support for mangling? And what tools actually need it? I also wonder if we need more from a demangler than just a string. I know linker

On Mon, Mar 02, 2015 at 12:12:34AM -0500, John Criswell wrote: > On 3/2/15 12:07 AM, Haopeng Liu wrote: > >Got it, thanks. But in my pass, I use function name to locate. Can I > >disable mangling in clang? > > No, but you can probably fine a library that can either mangle the original > name or demangle the name you're seeing in the LLVM bitcode. > > As an FYI,

...float *, float *, float *) but to call this function from R using .C() I have had to use the mangled version of this function name, gaRemin__FPiPfT1T0T1N41 Is using the mangled name my best option, or is there some way that R knows to interpret unmangled function names from C++ shared library objects? I'm concerned about portability of the resultant code in the case that name-mangling is handled differently from platform to platform. This is Linux, Redhat 7.2 with g++-2.96. Thanks for any hel...

...project that's partially bitcode and partially native > code, should lld allow linking a native .o to a bitcode .o? > > > > specifically in my case, I've got an stdcall function in bitcode, called > by native code, but it can't find the symbol (bitcode has it > > unmangled, native code with _ and @20) > > > When having thinlto enabled in both ends the same thing happens (but > bitcode on both ends works fine) > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > http://lists.llvm.org/...

...ally bitcode and partially native >> code, should lld allow linking a native .o to a bitcode .o? >> > >> > specifically in my case, I've got an stdcall function in bitcode, >called >> by native code, but it can't find the symbol (bitcode has it >> > unmangled, native code with _ and @20) >> >> >> When having thinlto enabled in both ends the same thing happens (but >> bitcode on both ends works fine) >> _______________________________________________ >> LLVM Developers mailing list >> llvm-dev at lists.llvm.org...

...fore attempting the move to Orc v2. But when I do that, some code which compiles fine with LLVM 7 breaks. I might get an undefined symbol like the following when I try to resolve a symbol defined by the code, after running constructors (successfully): _ZNSt6vectorIfSaIfEE17_M_default_appendEm Unmangled, that's: std::vector<float, std::allocator<float> >::_M_default_append(unsigned long) which is a function template defined by the C++ vector header file. If I add an explicit instanciation like so: template class std::vector<float>; the problem goes away. I have...

...ote: > When having a project that's partially bitcode and partially native code, should lld allow linking a native .o to a bitcode .o? > > specifically in my case, I've got an stdcall function in bitcode, called by native code, but it can't find the symbol (bitcode has it > unmangled, native code with _ and @20) When having thinlto enabled in both ends the same thing happens (but bitcode on both ends works fine)

We have built a tool which will take in a CDFG (in a particular format) and do some design automation based on it. The effort is to extend this tool to take an input from in the form of a systemC (extension of C++) code. The IR was used to generate the CDFG of the source code. But the requirement is to generate the CDFG of only a specific function and hence I am looking to iterate over the member

Hi all, Finally I managed to find out a strange problem under Visual C During the link of the HowToUseJIT program, I was always missing some symbols... and I was going crazy testing out different options... At the end, unmangling the differences in what linker was searching and what was present in the libraries, I found that the problem is that we have something like this... Value.h struct Value { bla bla bla } and around in the other files: SlotCalculator.h SchedGraph.h <big snip> class Value; The linker com...

...ates the undefined symbol error. We use DynamicLibrary::LoadLibraryPermanently(nullptr) to add process symbols. > Could you please share us the for what symbols you get undefined references :-) Certainly! Mangled: _ZNSi4swapERSi _ZNSt13basic_filebufIcSt11char_traitsIcEE4swapERS2_ And unmangled: std::basic_istream<char, std::char_traits<char> >::swap(std::basic_istream<char, std::char_traits<char> >&) std::basic_filebuf<char, std::char_traits<char> >::swap(std::basic_filebuf<char, std::char_traits<char> >&) Incidentally,...

Sorry yes, peter is the unmangled user name. On Fri, Nov 4, 2016 at 2:18 AM, Steffen Kaiser < skdovecot at smail.inf.fh-brs.de> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Thu, 3 Nov 2016, Peter Fraser wrote: > > The command doveadm user -u username successfully returns the username a...

...partially native >>> code, should lld allow linking a native .o to a bitcode .o? >>> > >>> > specifically in my case, I've got an stdcall function in bitcode, >>> called by native code, but it can't find the symbol (bitcode has it >>> > unmangled, native code with _ and @20) >>> >>> >>> When having thinlto enabled in both ends the same thing happens (but >>> bitcode on both ends works fine) >>> _______________________________________________ >>> LLVM Developers mailing list >>&gt...

...process >> symbols. >> >> > Could you please share us the for what symbols you get undefined >> references :-) >> >> Certainly! Mangled: >> >> _ZNSi4swapERSi >> _ZNSt13basic_filebufIcSt11char_traitsIcEE4swapERS2_ >> >> And unmangled: >> >> std::basic_istream<char, std::char_traits<char> >> >::swap(std::basic_istream<char, std::char_traits<char> >&) >> std::basic_filebuf<char, std::char_traits<char> >> >::swap(std::basic_filebuf<char, std::char_t...