similar to: [LLVMdev] LLVM_REQUIRES_EH

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

Hi, I am trying to implement a scenario similar to running ExceptionDemo.cpp with parameter -1 (where the JITed code calls the C++ function which throws an exception) Different from the given example I am using IRParser instead of IRBuilder. I can successfully catch the exception in Linux but the program crashes in Mac and Windows. The code is similar to as follows: ### The test.cpp :

Hi all, I have the following code: [use llvm to generate ir_func() ] in side the ir_func() there's a call to a native cpp function that throws an exception. (Just imagine changing the fibonacci 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

On Thu, Oct 14, 2010 at 4:09 PM, Duncan Sands <baldrick at free.fr> wrote: > Hi Francois, > >> In that case, RTTI and exception should also be disabled from CMake >> generated projects right? >> Currently they are enabled all over my MSVC projects. > > I'm not sure what you are asking.  The goal is for LLVM to not require > RTTI or exception handling.

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

Yes, I did -- it made no difference. Should it? Note that I have since discovered that this is not a problem on Windows -- the exception drops through as expected. pz On 2011-07-21, at 5:45 PM, Garrison Venn wrote: > Sorry Peter, just saw this. > > If you are still having the problem: > > Did you set: llvm::JITExceptionHandling = true; ? > > Garrison > > On Jul

Hi Chris, The MCSymbol r98459 patch of llvm seems to have broken the ExceptionDemo example. As the example is dying in the associated personality's first unwind search phase, which happens to have no language specific context, and is returning a _URC_CONTINUE_UNWIND, I believe the issue is generic and not specific to the example. However I'm not sure why then this wasn't seen in one

Ok, I've isolated the recent additions that cause the issue and supplied a patch which is NOT meant to be applied, but instead solely exists for identification purposes for those who know what they are doing. :-) The patch is offset from HEAD. The patch is a hack which removes use of the MCSymbol::isDefined(...) method, as its use happens to break in the exception JIT context; both in

Ok, see llvm/examples/ExceptionDemo/ExceptionDemo.cpp For OS X and Linux, build llvm with the environmental variable BUILD_EXAMPLES set to 1(csh: setenv BUILD_EXAMPLES 1). If llvm is already built, it will only build the examples from clang and llvm, ExceptionDemo being one of those. If I understand your case, running ExceptionDemo with an arg of -1 emulates your scenario. Note that the

Hi Garrison, Does r101453 fix this? -Chris On Mar 22, 2010, at 12:35 PM, Garrison Venn wrote: > Ok, I've isolated the recent additions that cause the issue and supplied a patch which is NOT meant > to be applied, but instead solely exists for identification purposes for those who know what they are doing. :-) > The patch is offset from HEAD. > > The patch is a hack which

Forgot to add platform with issue: OS X 10.6.2. I have not tested elsewhere. Garrison On Mar 18, 2010, at 14:20, Garrison Venn wrote: > Hi Chris, > > The MCSymbol r98459 patch of llvm seems to have broken the ExceptionDemo example. As the example is dying in the > associated personality's first unwind search phase, which happens to have no language specific context, and is

Hi, in ExceptionDemo code ( https://llvm.org/viewvc/llvm-project/llvm/trunk/examples/ExceptionDemo/ExceptionDemo.cpp?view=markup&sortby=file ) the function "ourPersonality" is defined. a llvm::Function is created with the same name inside function "createStandardUtilityFunctions". The llvm::Function is retrieved in function "createCatchWrappedInvokeFunction".

On Tue, Jul 12, 2011 at 07:25:16PM -0400, Peter Zion said > Hi All, > > I'm trying to catch an exception that is "passed through" an LLVM ExecutionEngine but I am unable to do so. Specifically, in C++ code, inside a try/catch block, I call a JITted function, which in turn calls back into my code. Everything works fine unless an exception is thrown; I would except the

Sorry, these IRBuilder methods are really in IRBuilderBase. Garrison On Jul 11, 2011, at 11:54, Garrison Venn wrote: > Are the get type methods for IRBuilder, such as const IntegerType *getInt32Ty(), going to have > their return type const qualifiers removed? Doing so would match the semi equivalent static > methods of Type, such as static IntegerType *getInt32Ty(LLVMContext &C).

I'm seeing the following result on code which has run successfully before on Linux, and currently successfully runs on OS X 10.6.x: Stack dump: 0. Running pass 'X86 DAG->DAG Instruction Selection' on function '@outerCatchFunct' Segmentation fault This process was built as part of the LLVM tree with: setenv CC /usr/local/bin/gcc setenv CFLAGS -march=i686 setenv CXX

---------- Forwarded message ---------- From: charles quarra <charllsnotieneningunputocorreo at gmail.com> Date: 2012/12/13 Subject: error while linking modules with exception handling demo code To: llvmdev at cs.uiuc.edu Hi, I am building a module X with an arithmetic function foo, a module Y with an arithmetic function foo2 that invokes foo. For the invocation be a proper one (being

Hi All, I'm trying to catch an exception that is "passed through" an LLVM ExecutionEngine but I am unable to do so. Specifically, in C++ code, inside a try/catch block, I call a JITted function, which in turn calls back into my code. Everything works fine unless an exception is thrown; I would except the outermost try/catch(...) block to catch the exception thrown in my innermost

Attached is a patch for the non ExceptionDemo demos which gets rid of the old const qualifier usage for Type. Although I recently commited the ExceptionDemo changes, I did not want to touch code that I did not "own" without other's approval. Even though trivial, I did not test this patch. Garrison -------------- next part -------------- A non-text attachment was scrubbed... Name:

Hi Osman, You can’t enable the static CRT through the command-line. You would need to apply this patch: https://reviews.llvm.org/D55056 (although it doesn’t work with lldb) Alex. ________________________________ De : llvm-dev <llvm-dev-bounces at lists.llvm.org> de la part de Osman Zakir via llvm-dev <llvm-dev at lists.llvm.org> Envoyé : 28 octobre 2019 07:47:43 À : llvm-dev at

Trying to get the Pure compiler to work with LLVM 3.1, I've run into a problem. The release notes say: "Target specific options have been moved from global variables to members on the new TargetOptions class, which is local to each TargetMachine." Unfortunately, they don't say anything about how to fix existing source to work around this. In my application I create a JIT