commit c982f45466ece6038a3dea103f07fc40a3aeaad0
parent 83676812d584443a5a44537dc6589d896c475343
Author: Vincent Forest <vincent.forest@meso-star.com>
Date: Mon, 23 Nov 2015 13:09:25 +0100
Re-enable the deserialisation test with CL19 compiler
The rewrite of the KISS deserialisation routine fixes the CL19 issue with the
fscanf function on empty stream (commit 77ec5d26).
Diffstat:
1 file changed, 0 insertions(+), 8 deletions(-)
diff --git a/src/test_ssp_rng.c b/src/test_ssp_rng.c
@@ -178,15 +178,7 @@ test_rng(const struct ssp_rng_type* type)
CHECK(ssp_rng_read(NULL, NULL), RES_BAD_ARG);
CHECK(ssp_rng_read(rng, NULL), RES_BAD_ARG);
CHECK(ssp_rng_read(NULL, stream), RES_BAD_ARG);
-
-#if !defined(COMPILER_CL) || _MSC_VER!=1900
- /* Actually, this check works propertly with the CL compiler but will lead to
- * an inexplicable error in the next check. It seems that reading from a
- * stream in "w+" mode whose pointer is EOF corrupts the stream when the code
- * is compiled with CL19! So, simply disable this check when this compiler is
- * used */
CHECK(ssp_rng_read(rng, stream), can_rw ? RES_IO_ERR : RES_BAD_OP);
-#endif
rewind(stream);
CHECK(ssp_rng_read(rng, stream), can_rw ? RES_OK : RES_BAD_OP);