Hi Toby, >> Thanks! The numerical errors with element-wise operations such as tan() >> or sin() look okay, that's just numerical noise. The following test >> cases deserve a closer look, though: >> >> test_matrix_matrix_trans_isub_C_float32 >> test_matrix_matrix_slice_trans_isub_C_float32 >> test_matrix_matrix_trans_isub_F_float32 >> test_matrix_range_matrix_slice_trans_iadd_C_float32 >> test_matrix_slice_matrix_slice_trans_iadd_C_float32 >> test_matrix_slice_matrix_trans_iadd_F_float32 >> test_matrix_matrix_range_trans_isub_C_float32 >> test_matrix_slice_matrix_trans_iadd_C_float32 >> test_matrix_matrix_slice_trans_isub_F_float32 >> test_matrix_matrix_range_trans_iadd_C_float32 >> test_matrix_range_matrix_trans_isub_C_float32 >> test_matrix_slice_matrix_slice_trans_isub_C_float32 >> test_matrix_slice_matrix_trans_isub_F_float32 >> test_matrix_matrix_range_trans_iadd_F_float32 >> test_matrix_slice_matrix_trans_isub_C_float32 >> test_matrix_matrix_slice_trans_iadd_C_float32 >> test_matrix_range_matrix_range_trans_isub_C_float32 >> test_matrix_range_matrix_trans_isub_F_float32 >> test_matrix_range_matrix_slice_trans_isub_C_float32 >> test_matrix_slice_matrix_range_trans_iadd_F_float32 >> test_matrix_range_matrix_range_trans_iadd_C_float32 >> test_matrix_slice_matrix_range_trans_isub_F_float32 >> test_matrix_range_matrix_trans_iadd_C_float32 >> test_matrix_slice_matrix_slice_trans_iadd_F_float32 >> test_matrix_range_matrix_trans_iadd_F_float32 >> test_matrix_slice_matrix_range_trans_iadd_C_float32 >> test_matrix_matrix_trans_iadd_F_float32 >> test_matrix_matrix_trans_iadd_C_float32 >> test_matrix_slice_matrix_slice_trans_isub_F_float32 >> test_matrix_range_matrix_slice_trans_isub_F_float32 >> test_matrix_matrix_range_trans_isub_F_float32 >> test_matrix_range_matrix_range_trans_isub_F_float32 >> test_matrix_slice_matrix_range_trans_isub_C_float32 >> test_matrix_range_matrix_range_trans_iadd_F_float32 >> >> Apparently they all belong to the same family of operations. Can you >> please help me with the deciphering? Which operations correspond to the >> test cases above? (I could guess, but I may be wrong...) iadd and isub >> refer to += and -=? > > Yep. So 'C' and 'F' mean C (row-major) layout or Fortran (col-major) layout. > Your guess was right about 'iadd' and 'isub': these are simply A += B > and A -= B. The values of A and B are given by the "_matrix_" bits: the > first one describes A, and the second describes B. So > "test_matrix_slice_matrix_range_trans_isub_C_float32" means > > matrix_slice -= matrix_range.T > > where both are C-layout and single precision.
okay, these should be working now, I've pushed a fix. :-) Still need to look into the GMRES issue... Best regards, Karli ------------------------------------------------------------------------------ _______________________________________________ ViennaCL-devel mailing list ViennaCL-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viennacl-devel
