search for: exceptiondemo

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...

...In 2.7 JITDwarfException:: EmitFrameMoves(...) used to check if the associated label id was deleted or folded into another. I guess the intent may now be to have this happen automatically to MCSymbol instances? I understand that trunk is being heavily thrashed in this area. Do you want me to turn ExceptionDemo into a related unit test case even though it only works on x86/x86_64 on UNIX systems, and requires exceptions to be turned on? Garrison On Mar 18, 2010, at 14:41, Garrison Venn wrote: > Forgot to add platform with issue: OS X 10.6.2. I have not tested elsewhere. > > Garrison > &g...

...ption:: > EmitFrameMoves(...) used to check if the associated label id was deleted or folded into another. I guess the > intent may now be to have this happen automatically to MCSymbol instances? > > I understand that trunk is being heavily thrashed in this area. Do you want me to turn ExceptionDemo into a related unit > test case even though it only works on x86/x86_64 on UNIX systems, and requires exceptions to be turned on? > > Garrison > > On Mar 18, 2010, at 14:41, Garrison Venn wrote: > >> Forgot to add platform with issue: OS X 10.6.2. I have not tested elsewh...

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 returning > a _URC_CONTINUE_UNWIND, I believe the issue is generic and not specific to the example. However I'm not sure why then &g...

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...

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

...andards, and is therefore not the same source as what results from applying the attached patch. The example's documentation fully explains how to run the example. Comments would be very useful. ;-) Garrison -------------- next part -------------- A non-text attachment was scrubbed... Name: ExceptionDemo.patch Type: application/octet-stream Size: 86667 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100115/bacc6329/attachment.obj>

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::Func...

...the effect of __attribute__((__aligned__))). Although this effort was taken on for my own edification, and an experimental use in a function pass, it can be made available to the list, if this list so desires. :-) -------------- next part -------------- A non-text attachment was scrubbed... Name: ExceptionDemo2.patch Type: application/octet-stream Size: 87961 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100202/c244dfe8/attachment.obj>

...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 able to handle exceptions correctly) i incorporated a third module that has defined exception-handling code that i've taken from the ExceptionDemo sample. First i'll post the module dump, the failed assertion and then i'll explain a bit about how do i generate the code: this is the module ExecutableCodeModule dump, which is the module that is used by the ExecutionEngine (not using new MCJIT, but it is not relevant for this question,...

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 -----...

...eep into building another local configuration, and debugging this, would someone be willing to test this on their version of a llvm linux installation? To build the test do the equivalent of: 1) setenv BUILD_EXAMPLES 1 2) make at the top of the llvm tree Then run: <release type>/examples/ExceptionDemo 2 3 7 -1 at the top of the llvm object root where <release type> == Release+Asserts for example Thanks in advance Garrison

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).

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

...onality catch i8* inttoptr (i64 987 to i8*) catch i8* inttoptr (i64 2453 to i8*) In my exception handler I walk through the records. I always get the correct count, but I type_table information isn't communicated: both of these records give me a type_offset of 1 (to use the ExceptionDemo's name of that field). I have cross-referenced this walking code with that demo, the gcc sources, and the third party (where it originated) and this aspect seems to be correct. Also, if I mark it as cleanup it'll get a 0 offset as expected (or no record if there are no catch clauses). The...

...f 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_RTTI but it doesn't seems to work. I also tested it with /EHs /EHsc in msvc. It makes no difference I also looked at the ExceptionDemo.cpp, but it seems to be unsupported under windows. Do I need to try catch and retrhow in my ir_func() ? Regards, -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160121/ccc8473f/attachment.html>

...you need to reconstitute the structure (for the 'resume' instruction), you can use the 'insertvalue' instruction. The code it produces is more verbose, but after optimizations, code-gen typically doesn't produce a lot of code for these sequences. I copied that bit of code from ExceptionDemo.cpp (lines 1270-1290): > llvm::LandingPadInst *caughtResult = > builder.CreateLandingPad(ourCaughtResultType, > personality, > numExceptionsToCatch, > "landingPad"); > // ......

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

Hello Albert, > Any help is much appreciated. I believe examples/ExceptionDemo contains sample code which sets TargetOptions flags. In particular, llvm::EngineBuilder class has setTargetOptions() method which does all necessary magic here. -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University