The unified version of arrayfire, an std::exception is throw while collecting the arrayfire global error message.
Now the arrayfire error message is collected from the correct platform, resulting in the throwing of an af::exception filled with info.
When checking the unified tests: 18 tests failed because an unexpected exception was thrown
Description
When collecting the error message from the underlying platform, the address of the corresponding function was incorrect, resulting in an access violation.
Result:
- Yes, an exception was thrown
- No, af::exception was not thrown, so no info on the real error
Changes to Users
None
Checklist
- Rebased on latest master
- Code compiles
- Tests pass
- Functions added to unified API
- Functions documented