qemu/tests/tcg/cris/check_addc.c
Rabin Vincent 21ce148c7e tests: cris: force inlining
The CRIS tests expect that functions marked inline are always inline.
With newer versions of GCC, building them results warnings like the
following and spurious failures when they are run.

In file included from tests/tcg/cris/check_moveq.c:5:0:
tests/tcg/cris/crisutils.h:66:20: warning: inlining failed in call to
'cris_tst_cc.constprop.0': call is unlikely and code size would grow [-Winline]
tests/tcg/cris/check_moveq.c:28:13: warning: called from here [-Winline]

Use the always_inline attribute when building them to fix this.

Reviewed-by: Edgar E. Iglesias <edgar.iglesias@xilinx.com>
Signed-off-by: Rabin Vincent <rabinv@axis.com>
Signed-off-by: Edgar E. Iglesias <edgar.iglesias@xilinx.com>
2016-09-28 10:45:44 +02:00

59 lines
1.3 KiB
C

#include <stdio.h>
#include <stdlib.h>
#include <stdint.h>
#include "sys.h"
#include "crisutils.h"
static always_inline int cris_addc(int a, const int b)
{
asm ("addc\t%1, %0\n" : "+r" (a) : "r" (b));
return a;
}
#define verify_addc(a, b, res, n, z, v, c) \
{ \
int r; \
r = cris_addc((a), (b)); \
cris_tst_cc((n), (z), (v), (c)); \
if (r != (res)) \
err(); \
}
int main(void)
{
cris_tst_cc_init();
asm volatile ("clearf cz");
verify_addc(0, 0, 0, 0, 0, 0, 0);
cris_tst_cc_init();
asm volatile ("setf z");
verify_addc(0, 0, 0, 0, 1, 0, 0);
cris_tst_cc_init();
asm volatile ("setf cz");
verify_addc(0, 0, 1, 0, 0, 0, 0);
cris_tst_cc_init();
asm volatile ("clearf c");
verify_addc(-1, 2, 1, 0, 0, 0, 1);
cris_tst_cc_init();
asm volatile ("clearf nzv");
asm volatile ("setf c");
verify_addc(-1, 2, 2, 0, 0, 0, 1);
cris_tst_cc_init();
asm volatile ("setf c");
verify_addc(0xffff, 0xffff, 0x1ffff, 0, 0, 0, 0);
cris_tst_cc_init();
asm volatile ("clearf nzvc");
verify_addc(-1, -1, 0xfffffffe, 1, 0, 0, 1);
cris_tst_cc_init();
asm volatile ("setf c");
verify_addc(0x78134452, 0x5432f789, 0xcc463bdc, 1, 0, 1, 0);
pass();
return 0;
}