Hi, At present there are a bunch of asserts for scenarios not handled by Sparse LLVM backend. A more robust error handling method is needed that works even in release builds, and doesn't abort the process. Given the way the code is structured currently, I was thinking maybe it will be easiest to use setjmp/longjmp mechanism to terminate the LLVM backend on error. I am not sure that this entirely safe with LLVM as the LLVM code is C++ - I think it might be okay as long as the LLVM module / context is properly disposed at the end. Regards Dibyendu -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
