Hey, > After cutting the matrix size down to 1000 the program didn't crash, but > the procedure took way too long (since I'm using ublas). Cutting the > size to 100 makes it ok, but there's a different problem now. > > As soon as the benchmark starts doing tests with the generated matrix, > it crashes my AMD display driver. The benchmark crashes at this point: > ublas_vec1 = boost::numeric::ublas::prod(ublas_matrix, ublas_vec2); > > ublas_vec2 is the vector read from the testdata file ( result65025.txt > ). This obviously won't work until those vectors are taken care of. > Unfortunately, I have no idea what to do with them.
argl, this is crappy uBLAS again. I'll kick this out now, it only creates problems rather than solving them. Best regards, Karli ------------------------------------------------------------------------------ Infragistics Professional Build stunning WinForms apps today! Reboot your WinForms applications with our WinForms controls. Build a bridge from your legacy apps to the future. http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk _______________________________________________ ViennaCL-devel mailing list ViennaCL-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viennacl-devel
