search for: throwinfo

Displaying 3 results from an estimated 3 matches for "throwinfo".

Did you mean: _throwinfo
2016 Jun 10
2
Windows: How to catch C++ exceptions in runtime-compiled code?
...at C++Now. Chandler suggested that we post our problem to this mailing list, and that perhaps Reid Kleckner and/or other people here may have some hints. Any ideas would be highly appreciated! In our case the RaiseException API function does not find the correct catch pad, which may be caused by a ThrowInfo structure handed to _CxxThrowException being empty. Apart from getting this right, is there anything else we possibly miss? Windows API functions to be called for registering catch pads or so? Some more details: We're using Clang for compiling C++ code at runtime and the ORC libraries to load...
2020 Jan 13
2
Incorrect code generation when using -fprofile-generate on code which contains exception handling (Windows target)
...id @__llvm_profile_instrument_target(i64 %26, i8* bitcast ({ i64, i64, i64*, i8*, i8*, i32, [2 x i16] }* @"__profd_?run at test@@QEAAXPEAVbase@@H at Z" to i8*), i32 0) call void %25(%class.base* %1) [ "funclet"(token %20) ] call void @_CxxThrowException(i8* null, %eh.ThrowInfo* null) #15 [ "funclet"(token %20) ] unreachable Following this pass, this IR has been replaced with the following, causing a breakage to the original program. This is occurring because the instrumentation function call, "__llvm_profile_instrument_target", is not m...
2020 Jan 14
2
Incorrect code generation when using -fprofile-generate on code which contains exception handling (Windows target)
...strument_target(i64 %26, i8* bitcast ({ > i64, i64, i64*, i8*, i8*, i32, [2 x i16] }* @"__profd_?run at test > @@QEAAXPEAVbase@@H at Z" to i8*), i32 0) > call void %25(%class.base* %1) [ "funclet"(token %20) ] > call void @_CxxThrowException(i8* null, %eh.ThrowInfo* null) #15 [ > "funclet"(token %20) ] > unreachable > > Following this pass, this IR has been replaced with the following, > causing a breakage to the original program. This is occurring because the > instrumentation function call, "__llvm_profile_instrume...