maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/clang/test/CodeGen/arm-asm-warn.c

33 lines
1.4 KiB
C
Raw Normal View History

Recommit Eric's code to validate ASM string's constraints and modifiers. This code checks the ASM string to see if the output size is able to fit within the variable specified as the output. For instance, scalar-to-vector conversions may not really work. It's on by default, but can be turned off with a flag if you think you know what you're doing. This is placed under a flag ('-Wasm-operand-widths') and flag group ('-Wasm'). <rdar://problem/12284092> llvm-svn: 166737
2012-10-26 07:28:48 +08:00
// REQUIRES: arm-registered-target
Add error checking to reject neon_vector_type attribute on targets without NEON. Patch by Artyom Skrobov. llvm-svn: 190801
2013-09-17 02:07:35 +08:00
// RUN: %clang_cc1 -triple armv7 -target-feature +neon %s -emit-llvm -o /dev/null
Recommit Eric's code to validate ASM string's constraints and modifiers. This code checks the ASM string to see if the output size is able to fit within the variable specified as the output. For instance, scalar-to-vector conversions may not really work. It's on by default, but can be turned off with a flag if you think you know what you're doing. This is placed under a flag ('-Wasm-operand-widths') and flag group ('-Wasm'). <rdar://problem/12284092> llvm-svn: 166737
2012-10-26 07:28:48 +08:00
Don't warn if the input size is less than the register size. Also don't warn if the output size is greater than the register size. No truncation occurs with those. Reword warning to make it clearer what's the problem is. llvm-svn: 169054
2012-12-01 07:18:12 +08:00
char bar();
void t1(int x, char y) {
__asm__ volatile("mcr p15, 0, %1, c9, c12, 5;"
"mrc p15, 0, %0, c9, c13, 2;"
: "=r" (x)
: "r" (bar())); // no warning
Don't emit a warning with an input/output parameter. We assume the user knows what they're doing here. llvm-svn: 169059
2012-12-01 07:46:56 +08:00
__asm__ volatile("foo %0, %1"
: "+r" (x),
"+r" (y)
:);
Do not report -Wasm-operand-widths for ARM output operands. <rdar://14050337> We're getting reports of this warning getting triggered in cases where it is not adding any value. There is no asm operand modifier that you can use to silence it, and there's really nothing wrong with having an LDRB, for example, with a "char" output. llvm-svn: 183172
2013-06-04 07:57:13 +08:00
__asm__ volatile("ldrb %0, [%1]" : "=r" (y) : "r" (x)); // no warning
Don't warn if the input size is less than the register size. Also don't warn if the output size is greater than the register size. No truncation occurs with those. Reword warning to make it clearer what's the problem is. llvm-svn: 169054
2012-12-01 07:18:12 +08:00
}
// <rdar://problem/12284092>
Recommit Eric's code to validate ASM string's constraints and modifiers. This code checks the ASM string to see if the output size is able to fit within the variable specified as the output. For instance, scalar-to-vector conversions may not really work. It's on by default, but can be turned off with a flag if you think you know what you're doing. This is placed under a flag ('-Wasm-operand-widths') and flag group ('-Wasm'). <rdar://problem/12284092> llvm-svn: 166737
2012-10-26 07:28:48 +08:00
typedef __attribute__((neon_vector_type(2))) long long int64x2_t;
typedef struct int64x2x4_t {
int64x2_t val[4];
} int64x2x4_t;
int64x2x4_t t2(const long long a[]) {
int64x2x4_t r;
__asm__("vldm %[a], { %q[r0], %q[r1], %q[r2], %q[r3] }"
Rephrase asm_mismatched_size_modifier diagnostic. <rdar://problem/14050339> The text of this diagnostic was unnecessarily specific to the current ARM implementation of validateConstraintModifier, and it gave a potentially confusing suggestion for fixing the problem. The ARM-specific issue is not a big deal since that is the only target that currently does any checking of asm operand modifiers, but until my change in 183172 it was still wrong for output operands in the way that it referred to the value being truncated when put into a register, since output operands are retrieved from the registers instead of being put into them. The bigger problem is that its suggestion to "use a modifier" is wrong and confusing in the case where a "q" modifier is incorrectly used with an "r" constraint. In that case, the solution might well be to remove the modifier or perhaps change the constraint. It's better to just leave the diagnostic message more generic. llvm-svn: 183209
2013-06-04 14:10:09 +08:00
: [r0] "=r"(r.val[0]), // expected-warning {{value size does not match register size specified by the constraint and modifier}}
[r1] "=r"(r.val[1]), // expected-warning {{value size does not match register size specified by the constraint and modifier}}
[r2] "=r"(r.val[2]), // expected-warning {{value size does not match register size specified by the constraint and modifier}}
[r3] "=r"(r.val[3]) // expected-warning {{value size does not match register size specified by the constraint and modifier}}
Recommit Eric's code to validate ASM string's constraints and modifiers. This code checks the ASM string to see if the output size is able to fit within the variable specified as the output. For instance, scalar-to-vector conversions may not really work. It's on by default, but can be turned off with a flag if you think you know what you're doing. This is placed under a flag ('-Wasm-operand-widths') and flag group ('-Wasm'). <rdar://problem/12284092> llvm-svn: 166737
2012-10-26 07:28:48 +08:00
: [a] "r"(a));
return r;
}