llvm-mirror/test/ExecutionEngine/OrcMCJIT/eh.ll

; REQUIRES: cxx-shared-library
; RUN: %lli -jit-kind=orc-mcjit %s
; XFAIL: arm, cygwin, windows-msvc, windows-gnu
declare i8* @__cxa_allocate_exception(i64)
declare void @__cxa_throw(i8*, i8*, i8*)
declare i32 @__gxx_personality_v0(...)
declare void @__cxa_end_catch()
declare i8* @__cxa_begin_catch(i8*)

@_ZTIi = external constant i8*

define void @throwException() {
  %exception = tail call i8* @__cxa_allocate_exception(i64 4)
  call void @__cxa_throw(i8* %exception, i8* bitcast (i8** @_ZTIi to i8*), i8* null)
  unreachable
}

define i32 @main() personality i8* bitcast (i32 (...)* @__gxx_personality_v0 to i8*) {
entry:
  invoke void @throwException()
          to label %try.cont unwind label %lpad

lpad:
  %p = landingpad { i8*, i32 }
          catch i8* bitcast (i8** @_ZTIi to i8*)
  %e = extractvalue { i8*, i32 } %p, 0
  call i8* @__cxa_begin_catch(i8* %e)
  call void @__cxa_end_catch()
  br label %try.cont

try.cont:
  ret i32 0
}
Don't try to run MCJIT/OrcJIT EH tests when C++ library is statically linked These tests assumes availability of external symbols provided by the C++ library, but those won't be available in case when the C++ library is statically linked because lli itself doesn't need these. This uses llvm-readobj -needed-libs to check if C++ library is linked as shared library and exposes that information as a feature to lit. Differential Revision: https://reviews.llvm.org/D41272 llvm-svn: 321981 2018-01-08 03:48:41 +01:00			`; REQUIRES: cxx-shared-library`
[Orc][lli] Add a very simple Orc-based lazy JIT to lli. This ensures that we're building and testing the CompileOnDemand layer, at least in a basic way. Currently x86-64 only, and with limited to no library calls enabled (depending on host platform). Patches welcome. ;) To enable access to the lazy JIT, this patch replaces the '-use-orcmcjit' lli option with a new option: '-jit-kind={ mcjit \| orc-mcjit \| orc-lazy }'. All regression tests are updated to use the new option, and one trivial test of the new lazy JIT is added. llvm-svn: 233182 2015-03-25 13:11:48 +01:00			`; RUN: %lli -jit-kind=orc-mcjit %s`
[CMake] Use normalized Windows target triples Changes the default Windows target triple returned by GetHostTriple.cmake from the old environment names (which we wanted to move away from) to newer, normalized ones. This also requires updating all tests to use the new systems names in constraints. Differential Revision: https://reviews.llvm.org/D47381 llvm-svn: 339307 2018-08-09 04:16:18 +02:00			`; XFAIL: arm, cygwin, windows-msvc, windows-gnu`
[Orc] Regression tests for OrcMCJITReplacement. Duplicated from the MCJIT regression tests. llvm-svn: 227780 2015-02-02 06:04:55 +01:00			`declare i8* @__cxa_allocate_exception(i64)`
			`declare void @__cxa_throw(i8, i8, i8*)`
			`declare i32 @__gxx_personality_v0(...)`
			`declare void @__cxa_end_catch()`
			`declare i8* @__cxa_begin_catch(i8*)`

			`@_ZTIi = external constant i8*`

			`define void @throwException() {`
			`%exception = tail call i8* @__cxa_allocate_exception(i64 4)`
			`call void @__cxa_throw(i8* %exception, i8* bitcast (i8** @_ZTIi to i8), i8 null)`
			`unreachable`
			`}`

Move the personality function from LandingPadInst to Function The personality routine currently lives in the LandingPadInst. This isn't desirable because: - All LandingPadInsts in the same function must have the same personality routine. This means that each LandingPadInst beyond the first has an operand which produces no additional information. - There is ongoing work to introduce EH IR constructs other than LandingPadInst. Moving the personality routine off of any one particular Instruction and onto the parent function seems a lot better than have N different places a personality function can sneak onto an exceptional function. Differential Revision: http://reviews.llvm.org/D10429 llvm-svn: 239940 2015-06-17 22:52:32 +02:00			`define i32 @main() personality i8* bitcast (i32 (...)* @__gxx_personality_v0 to i8*) {`
[Orc] Regression tests for OrcMCJITReplacement. Duplicated from the MCJIT regression tests. llvm-svn: 227780 2015-02-02 06:04:55 +01:00			`entry:`
			`invoke void @throwException()`
			`to label %try.cont unwind label %lpad`

			`lpad:`
Move the personality function from LandingPadInst to Function The personality routine currently lives in the LandingPadInst. This isn't desirable because: - All LandingPadInsts in the same function must have the same personality routine. This means that each LandingPadInst beyond the first has an operand which produces no additional information. - There is ongoing work to introduce EH IR constructs other than LandingPadInst. Moving the personality routine off of any one particular Instruction and onto the parent function seems a lot better than have N different places a personality function can sneak onto an exceptional function. Differential Revision: http://reviews.llvm.org/D10429 llvm-svn: 239940 2015-06-17 22:52:32 +02:00			`%p = landingpad { i8*, i32 }`
[Orc] Regression tests for OrcMCJITReplacement. Duplicated from the MCJIT regression tests. llvm-svn: 227780 2015-02-02 06:04:55 +01:00			`catch i8* bitcast (i8** @_ZTIi to i8*)`
			`%e = extractvalue { i8*, i32 } %p, 0`
			`call i8* @__cxa_begin_catch(i8* %e)`
			`call void @__cxa_end_catch()`
			`br label %try.cont`

			`try.cont:`
			`ret i32 0`
			`}`