treewide: use C++ exceptions properly

Since the codebase is designed around proper C++ idioms such as RAII, it
makes sense to only use C++ exceptions internally instead of mixing
exceptions and error codes. The exceptions are now caught at top level
to preserve compatibility with the existing error code-based API.

Note that we deliberately do not catch C++ runtime errors (such as
`std::bad_alloc`) nor logic errors (aka failed assertions) because no
actual handling can ever happen for such errors.

However, in the C interface we do catch _all_ exceptions (...) and
convert them into a wild-card error code.

1 files changed, 1 insertions, 0 deletions

diff --git a/CMakeLists.txt b/CMakeLists.txt
index bf2a36dd..f388a8ab 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -169,6 +169,7 @@ set(SOURCES
   src/routines/common.cpp
   src/cache.cpp
   src/clblast.cpp
+  src/clblast_exceptions.cpp
   src/clblast_c.cpp
   src/routine.cpp
   src/utilities.cpp