similar to: [LLVMdev] Have you guys met this issue about "typeinfo" & "vtable" of ASTConsumer and PluginASTAction?

Hello Guys, From this morning, I have been always trying PrintFunctionNames - an example of clang, but during compiling I was always meeting "__ZTIN5clang15PluginASTActionE", referenced from: __ZTI24PrintFunctionNamesAction in PrintFunctionNames.cpp.o. In fact, I didn't have "__ZTIN5clang15PluginASTActionE" in the symbol table, only I have was

Hello Guys,From this morning, I have been always trying PrintFunctionNames - an example of clang, but during compiling I was always meeting "__ZTIN5clang15PluginASTActionE", referenced from: __ZTI24PrintFunctionNamesAction in PrintFunctionNames.cpp.o.In fact, I didn't have "__ZTIN5clang15PluginASTActionE" in the symbol table, only I have was

Hello Guys,From this morning, I have been always trying PrintFunctionNames - an example of clang, but during compiling I was always meeting "__ZTIN5clang15PluginASTActionE", referenced from: __ZTI24PrintFunctionNamesAction in PrintFunctionNames.cpp.o.In fact, I didn't have "__ZTIN5clang15PluginASTActionE" in the symbol table, only I have was

On 06/04/2012 02:00 PM, yangzhi0104 at sohu.com wrote: > Hello Guys, > > From this morning, I have been always trying PrintFunctionNames - an example of clang, but during compiling I was always meeting "__ZTIN5clang15PluginASTActionE", referenced from: > __ZTI24PrintFunctionNamesAction in PrintFunctionNames.cpp.o. > > In fact, I didn't have

Hi LLVM Devs, I am in the process of building my own plugin for Clang/LLVM in Windows on Visual Studio. I am having difficulty generating the .dll shared file to use at compile time. How have the .dlls corresponding to the example plugins been built? This works: clang -fplugin=C:/Users/User/llvm-project/build/Release/bin/PrintFunctionNames.dll -Xclang -plugin -Xclang print-fns test.c This

Hi, I am new to LLVM and CLANG, I want to write plugin for printing detailed information about source code such as member function, function calls etc. I have referred PrintFunctionNames.cpp, and on line documentation for it, still i am confused about implementation of functions ex:- from CallGraph.cpp i want to use VisitCallExpr(CallExpr *E) and void CallGraph::print(raw_ostream &OS),

CC: llvm-dev (Whoops.) On 12 January 2013 17:55, Stephen McGruer <stephen.mcgruer at gmail.com> wrote: > Off the top of my head it looks like you're trying to build the plugin 'in > tree'? (That is, within the source tree rather than in a build directory.) > You should build LLVM and Clang to, say, ~/llvm-build, and then go to >

Hi, I've been doing some experimenting to get a "big" DLL version of Clang working. This involves changes to LLVM as well as Clang, and might apply to doing a "big" DLL version of LLVM too (if that makes sense), so I'm posting this to both cfe-dev and llvmdev. Basically, I want to find out if this mechanism is acceptable, or what alternative I should pursue. I have a

Hello, I want to write my own plug-in. So when i tried to execute the PrintFumctionNames plug-in in llvm/tools/clang/examples/PrintFumctionNames i'm getting an error at first step of 'make' only. The error is : akash at ubuntu:~/llvm/tools/clang/examples/PrintFunctionNames$ make ../../../../Makefile.common:60: ../../../../Makefile.config: No such file or directory

Hi, In another post I was trying to find out how to use libc++ instead of libstdc++ when compiling llvm/clang. I couldnt find the a way to tell cmake to do that. So I switched to using configure to compile llvm/clang. But now I find that the artifacts produced are different. Here are the issues I see: - configure doesnt seem to respect '--prefix' option, it just puts

Hi, I'm trying to do a build and install on Windows 10 with Visual Studio 2015 Community Edition for the X86 and ARM targets, from the current release_40 branch. While compilation completes without error, the INSTALL target fails with the following error: 54> CMake Error at projects/compiler-rt/lib/builtins/cmake_install.cmake:34 (file): 54> file INSTALL cannot find 54>

On Sat, Jun 14, 2014 at 6:15 AM Joerg Sonnenberger <joerg at britannica.bec.de> wrote: > On Fri, Jun 13, 2014 at 08:34:03PM +0200, Akim Demaille wrote: > > > > Le 5 juin 2014 à 00:32, Rafael Espíndola <rafael.espindola at gmail.com> a > écrit : > > > > > I think the difference is actually in the c++ library. It looks like > > > libstdc++

Llvm typically doesn't build with RTTI enabled. Perhaps that's what you're running into? Jim On Dec 10, 2012, at 1:27 PM, Vladimir Pouzanov <farcaller at gmail.com> wrote: > Hi all. > > I fully understand that the problem is a bit OT for llvmdev, but I'm stuck for two days now and I really need some direct push. > > To the problem. I have a C++ shared

Vladimir Pouzanov <farcaller at gmail.com> writes: > On Dec 10, 2012, at 21:57, Jim Grosbach <grosbach at apple.com> wrote: >> Llvm typically doesn't build with RTTI enabled. Perhaps that's what >> you're running into? >> > I've actually tried to compile both LLVM and my lib with -frtti with > same results. Please show the exact commands

> -----Original Message----- > From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] > On Behalf Of Óscar Fuentes > > Vladimir Pouzanov <farcaller at gmail.com> writes: > > > On Dec 10, 2012, at 21:57, Jim Grosbach <grosbach at apple.com> wrote: > >> Llvm typically doesn't build with RTTI enabled. Perhaps that's what

Gordon Keiser <gkeiser at arxan.com> writes: > There is (was?) a CMake variable for this if you're going that route. > Setting LLVM_REQUIRES_RTTI=1 enabled an RTTI build that I haven't had > issues with. I don't know what the ./configure equivalent is, sorry. LLVM_REQUIRES_RTTI is an internal variable. It works as you say, but there is no guarantee about it. Adding a

Good. Copying llvmdev for the record. Vladimir Pouzanov <farcaller at gmail.com> writes: > Sorted it out. > > In the end, the working build commands for me were: > > % export CXXFLAGS=-frtti > % ../llvm-3.1/configure > --prefix=/Users/farcaller/Developer/Active/llvm-src/install-3.1 > --enable-debug-runtime --enable-debug-symbols --disable-docs > --disable-doxygen

On Fri, Jun 13, 2014 at 08:34:03PM +0200, Akim Demaille wrote: > > Le 5 juin 2014 à 00:32, Rafael Espíndola <rafael.espindola at gmail.com> a écrit : > > > I think the difference is actually in the c++ library. It looks like > > libstdc++ changed to always use strcmp of the typeinfo names: > > > >

Le 5 juin 2014 à 00:32, Rafael Espíndola <rafael.espindola at gmail.com> a écrit : > I think the difference is actually in the c++ library. It looks like > libstdc++ changed to always use strcmp of the typeinfo names: > > https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=149964 > > Should we do the same with libc++? What do people think about this issue?

I've actually tried to compile both LLVM and my lib with -frtti with same results. On Dec 10, 2012, at 21:57, Jim Grosbach <grosbach at apple.com> wrote: > Llvm typically doesn't build with RTTI enabled. Perhaps that's what you're running into? > > Jim -- Vladimir Pouzanov http://www.farcaller.net/ -------------- next part -------------- A non-text attachment