On 11/14/2014 01:02 PM, Taras Kondratiuk wrote:
On 11/14/2014 11:49 AM, Alexandru Badicioiu wrote:
Hi,
for build errors - which compiler/toolchain do you use? I did not modify
in any way compilation flags and I have no problem with building with a
PPC toolchain and also with the native gcc on my development machine? I
use CUnit-2.1-3.
WARNING: braces {} are not necessary for any arm of this statement
#304: FILE: test/cunit/crypto/odp_crypto_test_async_inp.c:114:
+ if (compl_new == ODP_BUFFER_INVALID) {
[...]
+ } else {
[...]
If we remove the braces the test will not compile, it seems the CUnit
macros are the problem.
I've notices the same issue with CUnit macros. But it is strange.
CU_ASSERT defined like
#define CU_ASSERT(value) \
{ CU_assertImplementation((value), __LINE__, #value, __FILE__, "",
CU_FALSE); }
So it already has {} around it.
Try to remove ";":
if (compl_new == ODP_BUFFER_INVALID)
CU_ASSERT(compl_event == buf)
else
CU_ASSERT(compl_event == compl_new);
I see that translation code added your ";" after CU_ASSERT.
if (compl_new == (0xffffffff))
{ CU_assertImplementation((compl_event == buf), 115, "compl_event ==
buf", "odp_crypto_test_async_inp.c", "", 0); };
else
{ CU_assertImplementation((compl_event == compl_new), 117,
"compl_event == compl_new", "odp_crypto_test_async_inp.c", "", 0); };
Maxim.
_______________________________________________
lng-odp mailing list
[email protected]
http://lists.linaro.org/mailman/listinfo/lng-odp
_______________________________________________
lng-odp mailing list
[email protected]
http://lists.linaro.org/mailman/listinfo/lng-odp
