From 367a9f28c18199d9b259f9c0fdf1365df3133931 Mon Sep 17 00:00:00 2001 From: Justin Bogner Date: Wed, 6 May 2015 23:19:35 +0000 Subject: InstrProf: Give coverage its own errors instead of piggy backing on instrprof Since the coverage mapping reader and the instrprof reader were emitting a shared set of error codes, the error messages you'd get back from llvm-cov were ambiguous about what was actually wrong. Add another error category to fix this. I've also improved the wording on a couple of the instrprof errors, for consistency. llvm-svn: 236665 --- llvm/lib/ProfileData/InstrProf.cpp | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'llvm/lib/ProfileData/InstrProf.cpp') diff --git a/llvm/lib/ProfileData/InstrProf.cpp b/llvm/lib/ProfileData/InstrProf.cpp index 900dff96739..92822a71402 100644 --- a/llvm/lib/ProfileData/InstrProf.cpp +++ b/llvm/lib/ProfileData/InstrProf.cpp @@ -29,13 +29,13 @@ class InstrProfErrorCategoryType : public std::error_category { case instrprof_error::eof: return "End of File"; case instrprof_error::bad_magic: - return "Invalid file format (bad magic)"; + return "Invalid profile data (bad magic)"; case instrprof_error::bad_header: - return "Invalid header"; + return "Invalid profile data (file header is corrupt)"; case instrprof_error::unsupported_version: - return "Unsupported format version"; + return "Unsupported profiling format version"; case instrprof_error::unsupported_hash_type: - return "Unsupported hash function"; + return "Unsupported profiling hash"; case instrprof_error::too_large: return "Too much profile data"; case instrprof_error::truncated: -- cgit v1.2.3