qemu-e2k/tests/tcg/cris/check_abs.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

41 lines
808 B
C

#include <stdio.h>
#include <stdlib.h>
#include <stdint.h>
#include "sys.h"
#include "crisutils.h"
static always_inline int cris_abs(int n)
{
int r;
asm ("abs\t%1, %0\n" : "=r" (r) : "r" (n));
return r;
}
static always_inline void
verify_abs(int val, int res,
const int n, const int z, const int v, const int c)
{
int r;
cris_tst_cc_init();
r = cris_abs(val);
cris_tst_cc(n, z, v, c);
if (r != res)
err();
}
int main(void)
{
verify_abs(-1, 1, 0, 0, 0, 0);
verify_abs(0x80000000, 0x80000000, 1, 0, 0, 0);
verify_abs(0x7fffffff, 0x7fffffff, 0, 0, 0, 0);
verify_abs(42, 42, 0, 0, 0, 0);
verify_abs(1, 1, 0, 0, 0, 0);
verify_abs(0xffff, 0xffff, 0, 0, 0, 0);
verify_abs(0xffff, 0xffff, 0, 0, 0, 0);
verify_abs(-31, 0x1f, 0, 0, 0, 0);
verify_abs(0, 0, 0, 1, 0, 0);
pass();
return 0;
}