Rafael Espindola 3ca4721c27 Use the DiagnosticHandler to print diagnostics when reading bitcode. ... The bitcode reading interface used std::error_code to report an error to the callers and it is the callers job to print diagnostics. This is not ideal for error handling or diagnostic reporting: * For error handling, all that the callers care about is 3 possibilities: * It worked * The bitcode file is corrupted/invalid. * The file is not bitcode at all. * For diagnostic, it is user friendly to include far more information about the invalid case so the user can find out what is wrong with the bitcode file. This comes up, for example, when a developer introduces a bug while extending the format. The compromise we had was to have a lot of error codes. With this patch we use the DiagnosticHandler to communicate with the human and std::error_code to communicate with the caller. This allows us to have far fewer error codes and adds the infrastructure to print better diagnostics. This is so because the diagnostics are printed when he issue is found. The code that detected the problem in alive in the stack and can pass down as much context as needed. As an example the patch updates test/Bitcode/invalid.ll. Using a DiagnosticHandler also moves the fatal/non-fatal error decision to the caller. A simple one like llvm-dis can just use fatal errors. The gold plugin needs a bit more complex treatment because of being passed non-bitcode files. An hypothetical interactive tool would make all bitcode errors non-fatal. llvm-svn: 225562		2015-01-10 00:07:30 +00:00
..
CMakeLists.txt	[CMake] Update LLVM_LINK_COMPONENTS for each CMakeLists.txt.	2013-12-10 11:13:32 +00:00
llvm-dis.cpp	Use the DiagnosticHandler to print diagnostics when reading bitcode.	2015-01-10 00:07:30 +00:00
LLVMBuild.txt	LLVMBuild: Remove trailing newline, which irked me.	2011-12-12 19:48:00 +00:00
Makefile	build: Tidy up a bunch of tool Makefiles, and simplify where possible using the	2011-10-18 19:27:24 +00:00