search for: llvm_enable_eh

...i example and calling a native c++ func that throws inside the fibonacci body) I can't seem to catch "foreign" exception or any exception using the following pseudo code: try { // cast function ptr and execute ir_func(); } catch (const myEx&) { } catch (...) { } Looking at: *LLVM_ENABLE_EH:BOOL*Build LLVM with exception-handling support. This is necessary if you wish to link against LLVM libraries and make use of C++ exceptions in your own code that need to propagate through LLVM code. Defaults to OFF. It seems to be exactly what I require. I enabled LLVM_ENABLE_EH and LLVM_ENABLE_R...

Can anyone think of a good reason to keep this CMake variable around? AFAICT llvm should never need to be compiled with exception support, and the same applies for clang, lldb, lld, and all (?) other LLVM subprojects. If there's no reason to keep this around I can just remove it entirely. -------------- next part -------------- An HTML attachment was scrubbed... URL:

...15639 abort (core dumped) ./main What can be the reason for the different behaviour in different platforms? In order to make it work, do I need to wrap the llvm::Function* f with the unwindResume and externalException blocks ? Any other suggestions ? By the way I use LLVM 3.6.0 compiled with LLVM_ENABLE_EH and RTTI enabled. Thanks in advance for your help. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150320/9b85b68c/attachment.html>

...rsions of the library have an issue, which causes occasional lldb crashes. See <https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59656> for details. Possible courses of action are: - use libstdc++ version 4.9 or newer - use libc++ (via LLVM_ENABLE_LIBCXX) - enable exceptions (via LLVM_ENABLE_EH) - ignore this warning and accept occasional instability Call Stack (most recent call first): tools/lldb/CMakeLists.txt:4 (include) --- libstdc++ is 6.2.1 so the CMake check seems wrong. This prompted me to use -libstd=libc++ and -DLLVM_ENABLE_LIBCXX=ON, but for some reason Arch Linux packag...

...mmand "cmake -S../llvm -G"Visual Studio 16 2019" -Thost=x64 -DCMAKE_INSTALL_PREFIX=../install -DCMAKE_BUILD_TYPE=Release -DCMAKE_MSVC_RUNTIME_LIBRARY=MT -DCMAKE_CXX_FLAGS="/permissive- /EHsc /std:c++17 /O2 /MT /D_SILENCE_ALL_CXX_DEPRECATION_WARNINGS" -DLLVM_ENABLE_RTTI=On -DLLVM_ENABLE_EH=ON -DCMAKE_CXX_STANDARD=17 -DPYTHON_HOME=C:/Users/Osman/AppData/Local/Programs/Python/Python38 -DLLVM_ENABLE_PROJECTS="clang;clang-tools-extra;lld;lldb;libcxx;libcxxabi"". But I still get "Using Release VC++ CRT: MD", and also the CMake warning: "CMake Warning at util...

I would really like to know about how to apply the patch for making MSVC-built LLVM executables lighter. But aside from that, I also want to know what LLVM does to CMake's default setting of /EHsc. I want to keep that setting on, but I can't figure out how. Any help is appreciated. Thanks in advance. P.S. The CMAKE_CXX_FLAGS variable isn't helping at all, otherwise I wouldn't

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

...; causes occasional lldb crashes. See > <https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59656> for details. > Possible > courses of action are: > > - use libstdc++ version 4.9 or newer > > - use libc++ (via LLVM_ENABLE_LIBCXX) > > - enable exceptions (via LLVM_ENABLE_EH) > > - ignore this warning and accept occasional instability > Call Stack (most recent call first): > tools/lldb/CMakeLists.txt:4 (include) > --- > > libstdc++ is 6.2.1 so the CMake check seems wrong. > Or maybe it is picking up a different libstdc++ from somewhere else...

On Tue, Dec 20, 2016 at 11:05 AM, Carsten Mattner <carstenmattner at gmail.com> wrote: > On Tue, Dec 20, 2016 at 5:05 PM, Teresa Johnson <tejohnson at google.com> > wrote: > > Hi Carsten, > > > > A few responses below, but first, can you get the link command for > > lldb.so.3.9.1? Last time it was the lldb.so build that was using > > ld.bfd with the

Hello, I get a crash in my program that uses exceptions and the LLVM JIT, even though the exceptions are controlled and thrown/catched in a part that doesn't deal with LLVM. I noticed that llvm-config --cxxflags includes the -fno-exceptions flag. Do I need to throw no exceptions whatsoever in my application to use LLVM JIT? As a minimal example, I modified the code in

Is there a simple method for compiling a custom assertion header/call into all the LLVM libraries? I want my application to be able to handle any thrown assertions (ie; as an exception) and recover or crash gracefully. I already have a custom header in place in the application's source, however this doesn't have an effect on [most of] the already compiled lib's. -------------- next

Hello, Le 12/12/2016 à 18:29, Hans Wennborg a écrit : > +Sylvestre who knows about these things. > > On Thu, Dec 8, 2016 at 2:24 AM, Kris van Rens via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> L.S., >> >> I'm currently in the process of creating Debian packages for >> clang/llvm release 3.9.0. For this I'm using the steps as explained on

On Mon, Mar 14, 2016 at 5:30 PM, Chris Bieneman <cbieneman at apple.com> wrote: [ brutal-snip ] ... > [ TODO#S: Before doing a 2nd build (and in a 3rd run using more > optimized binaries) ] > > How do I anable LTO via CMAKE? > > > LLVM_ENALBLE_LTO=On > [ v4 of my build-script attached ] Hi Chris, thanks for the response! That seems to work (see below). $ cd

Trying to run a self host "ninja check-clang" with ASan enabled I hit a /lot/ of errors like this (strangely I hit none of these in check-llvm, only in check-clang): Any ideas? ==10525==ERROR: AddressSanitizer failed to deallocate 0x10800 (67584) bytes at address 0x631000014800 ==10525==AddressSanitizer CHECK failed:

...LLVM_ENABLE_CRASH_OVERRIDES:BOOL=ON //Compile with C++1y enabled. LLVM_ENABLE_CXX1Y:BOOL=OFF //Debug: Prints tablegen patterns that were used for selecting LLVM_ENABLE_DAGISEL_COV:BOOL=OFF //Use doxygen to generate llvm API documentation. LLVM_ENABLE_DOXYGEN:BOOL=OFF //Enable Exception handling LLVM_ENABLE_EH:BOOL=OFF //Enable expensive checks LLVM_ENABLE_EXPENSIVE_CHECKS:BOOL=OFF //Use libffi to call external functions from the interpreter LLVM_ENABLE_FFI:BOOL=OFF //Use libc++ if available. LLVM_ENABLE_LIBCXX:BOOL=OFF //Use libedit if available. LLVM_ENABLE_LIBEDIT:BOOL=ON //Use lld as C and C++ l...