search for: requires_eh

Hi, It's good that llvm/lib builds with exceptions and RTTI disabled as it supports doing optimization and codegen on very constrained platforms. Judging by REQUIRES_EH in makefiles, only a few bits like TableGen, llvm-ar and llvm-ranlib need them, and I doubt these would need to run on a target. It's unlikely exceptions would get in in a random patch, because it would have to change the makefile; but even so, it would be useful to know that it's due to a...

Hi Al, > It's good that llvm/lib builds with exceptions and RTTI disabled as it > supports doing optimization and codegen on very constrained platforms. > Judging by REQUIRES_EH in makefiles, only a few bits like TableGen, llvm-ar > and llvm-ranlib need them, and I doubt these would need to run on a target. > It's unlikely exceptions would get in in a random patch, because it would > have to change the makefile; but even so, it would be useful to know that &gt...

...rameLowering::SpillSlot* llvm::PPCFrameLowering::getCalleeSavedSpillSlots(unsigned int&) const’: PPCFrameLowering.h:138:51: error: ‘X31’ is not a member of ‘llvm::PPC’ I'm using the same configure I did for 3.2 (well, I didn't explicitly set gcc before): export REQUIRES_RTTI=1 export REQUIRES_EH=1 export CC=gcc export CXX=g++ ./configure --prefix=/opt/llvm/install --enable-optimized --enable-shared --enable-libffi --enable-assertions --enable-doxygen Then I just run: make -- edA-qa mort-ora-y -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Sign: Please digitally...

On Thu, Aug 14, 2014 at 6:01 PM, Reid Kleckner <rnk at google.com> wrote: > I thought Linux distros compile LLVM with RTTI and exceptions enabled when > packaging. > The question is why. RTTI makes sense -- they may well need it. But exceptions should work fine in the rest of the application even if LLVM is compiled with them, no? -------------- next part -------------- An HTML

...y MSVC projects. On Thu, Oct 14, 2010 at 3:57 AM, Duncan Sands <baldrick at free.fr> wrote: > Hi Al, > >> It's good that llvm/lib builds with exceptions and RTTI disabled as it >> supports doing optimization and codegen on very constrained platforms. >> Judging by REQUIRES_EH in makefiles, only a few bits like TableGen, llvm-ar >> and llvm-ranlib need them, and I doubt these would need to run on a target. >> It's unlikely exceptions would get in in a random patch, because it would >> have to change the makefile; but even so, it would be useful to k...

...being compiled with symbols. > Did you verify that your sources are compiled with -g? I think so, this is the makefile (based on the one in the Hello pass): > LEVEL = ../../.. > LIBRARYNAME = CGF > LOADABLE_MODULE = 1 > USEDLIBS = > > ifneq ($(REQUIRES_RTTI), 1) > ifneq ($(REQUIRES_EH), 1) > EXPORTED_SYMBOL_FILE = $(PROJ_SRC_DIR)/CGF.exports > endif > endif > > include $(LEVEL)/Makefile.common and this is the invocation: > cafxx at ubuntu:~/Projects/llvm2/lib/Transforms/cgf$ make > llvm[0]: Compiling CGFPass.cpp for Debug+Asserts build (PIC) > llvm[0]: Li...

> You'll better investigate why exception support is required for MSYS > while all other configure-based builds work fine without it. Surely it's required for any system that uses lib/System/Win32/Signals.inc, because there's code in that file that uses try/catch. MingW is the only system I know of that uses that file; Cygwin pretends to be Unix-like, so it uses

Hi, I've written a CallGraphSCCPass that compiles successfully, but when I try to run it with opt, it fails: Symbol not found: __ZTIN4llvm16CallGraphSCCPassE If I simply change the pass to be a FunctionPass or a ModulePass, opt can run it just fine. I'm on Mac OS X, so I thought perhaps I was running into bug #2771 [1], but I'm getting the same error on Ubuntu Linux:

Hi Trevor, > I've written a CallGraphSCCPass that compiles successfully, but when I > try to run it with opt, it fails: > > Symbol not found: __ZTIN4llvm16CallGraphSCCPassE $ c++filt _ZTIN4llvm16CallGraphSCCPassE typeinfo for llvm::CallGraphSCCPass LLVM TOT has RTTI turned off as far as I know (not sure about 2.7). Are you making use of RTTI? Ciao, Duncan.

...op>::~LoopBase()' ScalarEvolutionTest.cpp:(.text+0x14fa): undefined reference to `llvm::LoopBase<llvm::BasicBlock, llvm::Loop>::~LoopBase()' clang: error: linker command failed with exit code 1 (use -v to see invocation) I compile with these options: export REQUIRES_RTTI=1 export REQUIRES_EH=1 ./configure --prefix=/opt/llvm/install --enable-optimized --enable-shared --enable-libffi --enable-assertions make > gcc --version gcc (Ubuntu/Linaro 4.6.3-1ubuntu5) 4.6.3 I was able to compile 3.1 previously. -- edA-qa mort-ora-y -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --...

While creating compiler transformations for use with opt, I discovered that when configuring and making LLVM and its projects, exceptions are disabled. I'm assuming that was done for performance reasons. Is there any reason not to enable exceptions for LLVM projects? Thanks, Ryan

...mplates and boost & stl libraries and I am using a slow machine. Specifically, I am looking for ways to change the Makefile and use precompiled headers and incremental linking, but still can't figure out how the Makefile is structured. compiler: gcc 4.2.0. build options: ENABLE_OPTIMIZED=0 REQUIRES_EH=1 Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20080216/2430d98c/attachment.html>

Pekka Jääskeläinen wrote: > Jeffrey Yasskin wrote: >> I've put together http://llvm.org/docs/Packaging.html to document >> these kinds of requests for all packagers in one place. Let me know if >> any of the advice I've put there is wrong. (At the moment, > > Looks good to me. BTW exception support for LLVM is not required > to link with code that uses

...Thu, Oct 14, 2010 at 3:57 AM, Duncan Sands<baldrick at free.fr> wrote: >> Hi Al, >> >>> It's good that llvm/lib builds with exceptions and RTTI disabled as it >>> supports doing optimization and codegen on very constrained platforms. >>> Judging by REQUIRES_EH in makefiles, only a few bits like TableGen, llvm-ar >>> and llvm-ranlib need them, and I doubt these would need to run on a target. >>> It's unlikely exceptions would get in in a random patch, because it would >>> have to change the makefile; but even so, it would be...

On Jun 24, 2011, at 10:14 AM, Carlo Alberto Ferraris wrote: > I'm working on a pass (both LLVM and the pass have been compiled in debug+asserts mode) but when the pass crashes in the stack trace printed by opt the names of the functions inside my pass don't appear (see frames 14-16). How can I have them displayed? >> cafxx at ubuntu:~/Projects/llvm2/Debug+Asserts/bin$ clear

...Did you verify that your sources are compiled with -g? > I think so, this is the makefile (based on the one in the Hello pass): >> LEVEL = ../../.. >> LIBRARYNAME = CGF >> LOADABLE_MODULE = 1 >> USEDLIBS = >> >> ifneq ($(REQUIRES_RTTI), 1) >> ifneq ($(REQUIRES_EH), 1) >> EXPORTED_SYMBOL_FILE = $(PROJ_SRC_DIR)/CGF.exports >> endif >> endif >> >> include $(LEVEL)/Makefile.common > and this is the invocation: >> cafxx at ubuntu:~/Projects/llvm2/lib/Transforms/cgf$ make >> llvm[0]: Compiling CGFPass.cpp for Debug+As...

Thanks a lot for the reply guys. So, does that mean that I cant write my own passes if I work on Windows side of the LLVM? Is there any other way to use a new pass. How are windows users supposed to work? Thanks again. On Sun, Apr 18, 2010 at 7:16 AM, Anton Korobeynikov <anton at korobeynikov.info > wrote: > > If you compile llvm, the Hello library will be compiled too. It's

> If you compile llvm, the Hello library will be compiled too. It's not > installed but it's in build_directory/Debug/lib/LLVMHello.so (or in > build_directory/Release/lib/LLVMHello.so) Loadable passes are not supported on windows due to lack of OS dynamic linking support (and I doubt they will be supported ever). -- With best regards, Anton Korobeynikov Faculty of Mathematics

Jeffrey Yasskin wrote: > I've put together http://llvm.org/docs/Packaging.html to document > these kinds of requests for all packagers in one place. Let me know if > any of the advice I've put there is wrong. (At the moment, Looks good to me. BTW exception support for LLVM is not required to link with code that uses exceptions. At least our toolset seems to link fine with LLVM

I'm working on a pass (both LLVM and the pass have been compiled in debug+asserts mode) but when the pass crashes in the stack trace printed by opt the names of the functions inside my pass don't appear (see frames 14-16). How can I have them displayed? > cafxx at ubuntu:~/Projects/llvm2/Debug+Asserts/bin$ clear && ./opt > -load=CGF.so -cgf -debug test.S > [...] >