similar to: [LLVMdev] Decoding munged function names

Hmm... looks like my LLVM build script only built debug versions of the tools, not release versions. I'm investigating, I didn't change anything that should have caused that. [s] On Apr 28, 2009, at 4:56 PM, Bill Wendling wrote: > On Tue, Apr 28, 2009 at 4:43 PM, Sarah Thompson <sarah at findatlantis.com > > wrote: >> OK, that got much further, but I'm now

(My script does both of those -- the debug build worked (I think), but the release build fails) [s] On Apr 28, 2009, at 5:19 PM, Bill Wendling wrote: > We build debug by default. You will have to add ENABLE_OPTIMIZED=1 on > the "make" command line or --enable-optimized during configuration. > > -bw > > On Tue, Apr 28, 2009 at 5:12 PM, Sarah Thompson <sarah at

We build debug by default. You will have to add ENABLE_OPTIMIZED=1 on the "make" command line or --enable-optimized during configuration. -bw On Tue, Apr 28, 2009 at 5:12 PM, Sarah Thompson <sarah at findatlantis.com> wrote: > Hmm... looks like my LLVM build script only built debug versions of > the tools, not release versions. I'm investigating, I didn't change

OK, that got much further, but I'm now seeing another problem which may (or may not) be related. Building my own code (my model checker), it builds libraries fine, then within tools (I'm using a fairly standard LLVM build environment here), I am seeing the error *** llvm-config doesn't exist - rebuilding it followed by a make: Entering an unknown directory which is

Hi folks, Assuming that I'm writing a pass and that for bizarre reasons I need to programmatically do the equivalent of a C/C++ sizeof on a Value (or a Type, it doesn't matter which really), yielding a result in bytes, what is the known-safe way to do this? I notice that doing something like struct thingy { ... some stuff ... }; ... printf("Size = %d",

A long time ago, when I devised the grammar and structure of the Microsoft C++ name mangling scheme (decorated names), the document describing the object model and the name decoration scheme were made publically available. Perhaps this is still available publically, or perhaps Microsoft might be willing to share an up to date definition of the name-decoration grammar, especially in light of the

Just to give closure here, I eventually gave up, built an Ubuntu 9 VMWare image which uses gcc 4.3.2 by default, installed Eclipse Ganymede and various other tools, then built LLVM 2.5 and my own code. It all ran fine. There is clearly something broken in the CentOS gcc43 package. Definitely one to avoid. [s] On Apr 28, 2009, at 5:40 PM, Sarah Thompson wrote: > (My script does both

On Tue, Apr 28, 2009 at 4:43 PM, Sarah Thompson <sarah at findatlantis.com> wrote: > OK, that got much further, but I'm now seeing another problem which > may (or may not) be related. Building my own code (my model checker), > it builds libraries fine, then within tools (I'm using a fairly > standard LLVM build environment here), I am seeing the error > >        ***

Hi, everyone! I'm new here trapped by a simple problem for days. When LLVM translates C++ source code to IR, it will add a prefix to the function name. For example: source code: int foo(){ return 1; } IR form: define i32 @_Z3foov() #0 { entry: ret i32 1, !dbg !20 } The getName() method returns _Z3foov, then how can I get foo? I know the debugging information is contained in

Hi, We have a demangler for the Itanium ABI, but looks like we don't have one for the MSVC-style symbols. Is there any good demangler we can import to LLVM? If there's no suitable demangler, I'd like to write one. Currently, we are using `UnDecorateSymbolName` function, but the function is available only on Windows (which is problematic when you are doing a cross-build), and the

Hello all, I'm getting started on a project using LLVM's opt tool to do static analysis, printing call graphs and such. When compiling C programs to IR (and eventually to call graphs), function names remain the same (main, function1, function2 etc.), but when compiling the same program as C++, the function names often have cruft added to them (_Z9function1v, _Z9function2v etc.) which

If you want to get the original name by a library function, as Jonathan mentioned, you can call __cxa_demangle in cxxabi.h. However, this API is only available in gcc. If you want something more portable, try glog or libibert, notice libibert is GPL licensed. On Thu, Dec 11, 2014 at 7:57 AM, Roel Jordans <r.jordans at tue.nl> wrote: > When a C++ compiler translates source code it will

Hi! A few of us over at Google think a nice feature in clang would be ODR violation checking, and we thought for a while about how to do this and wrote it down, but we aren't actively working on it at the moment nor plan to in the near future. I'm posting this to share our design and hopefully save anyone else the design work if they're interested in it. For some background, C++'s

Check out http://nondot.org/sabre/LLVMNotes -Chris http://nondot.org/sabre http://llvm.org On Jul 27, 2007, at 12:00 PM, Sarah Thompson <thompson at email.arc.nasa.gov > wrote: > Hi folks, > > Assuming that I'm writing a pass and that for bizarre reasons I need > to > programmatically do the equivalent of a C/C++ sizeof on a Value (or a > Type, it doesn't

Hi Renato, > > Just wondering if LLVM has any command options or tool to allow for > > demangling C++ names from the LLVM bitcode? > > c++filt? Do you refer to any particular version of c++filt? I tried, but seemed not to work. For example, when I run a command as below: c++filt _ZNSt4listIiSaIiEEaSERKS1_ The output remains the same as the input symbol. By the way,

Hey all, Just wondering if LLVM has any command options or tool to allow for demangling C++ names from the LLVM bitcode? Thanks! Best, Xiaolong

On 11 July 2013 18:02, John McCall <rjmccall at apple.com> wrote: > On Jul 11, 2013, at 5:45 PM, Nick Lewycky <nlewycky at google.com> wrote: > > Hi! A few of us over at Google think a nice feature in clang would be > ODR violation checking, and we thought for a while about how to do this and > wrote it down, but we aren't actively working on it at the moment nor

I have encountered a need for manually generating the mangled name of an arbitrary C++ function. The only way I currently know how to do this is to generate a dummy C++ source file, compile it, and look at the output. This approach is so ugly that I would like for it never to see the light of day. The c++filt tool generates demangled C++ names given the mangled ones, which is the opposite

On 27 August 2010 18:56, Xiaolong Tang <xiaolong.snake at gmail.com> wrote: > Just wondering if LLVM has any command options or tool to allow for > demangling C++ names from the LLVM bitcode? c++filt? --renato

On Jul 11, 2013, at 5:45 PM, Nick Lewycky <nlewycky at google.com> wrote: > Hi! A few of us over at Google think a nice feature in clang would be ODR violation checking, and we thought for a while about how to do this and wrote it down, but we aren't actively working on it at the moment nor plan to in the near future. I'm posting this to share our design and hopefully save anyone