search for: install_fatal_error_handl

...void win_abort_handler(int) { RaiseException(0, 0, 0, NULL); } void handle_llvm_fatal(void *User, const std::string &Reason) { std::cerr << "Caught LLVM ERROR: " << Reason << "\n"; abort(); // Chains to win_abort_handler on Windows } int main() { install_fatal_error_handler(handle_llvm_crash, NULL); signal(SIGABRT, win_abort_handler); _set_abort_behavior(0, _WRITE_ABORT_MSG | _CALL_REPORTFAULT); llvm_start_multithreaded(); ContextRecoveryContext::Enable(); // "safe" calls with RunSafely() ContextRecoveryContext::Disable(); return 0; } D...

...was changed in an incompatible way too. Are there any other intrinsics that changed? 4. SetCurrentDebugLocation takes a DebugLoc now 5. VISIBILITY_HIDDEN is gone 6. SMDiagnostic takes different parameters 7. APIs renamed: llvm_report_error -> report_fatal_error llvm_install_error_handler -> install_fatal_error_handler llvm::DwarfExceptionHandling -> llvm::JITExceptionHandling 8. disable calls to memory_barrier. this is not correct for SMP but at least its not crashing. I'll probably have more to add to this list once I try to port our bytecode compiler. > Leading up to that date, > please make s...

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

Good news, everybody! It's that time of year again. We are going to release LLVM 2.8! I'm taking over for Tanya to give her a much needed break. I can only hope to perform as well as she has. This is my first time as release manager, so bear with me if things don't go smoothly. This message is mostly to give you an idea of the schedule we're planning on. It's an aggressive