21ce148c7e
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>
19 lines
411 B
C
19 lines
411 B
C
#include <unistd.h>
|
|
|
|
#define STRINGIFY(x) #x
|
|
#define TOSTRING(x) STRINGIFY(x)
|
|
|
|
#define always_inline inline __attribute__((always_inline))
|
|
|
|
#define CURRENT_LOCATION __FILE__ ":" TOSTRING(__LINE__)
|
|
|
|
#define err() \
|
|
{ \
|
|
_fail("at " CURRENT_LOCATION " "); \
|
|
}
|
|
|
|
#define mb() asm volatile ("" : : : "memory")
|
|
|
|
void pass(void);
|
|
void _fail(char *reason);
|