================
@@ -0,0 +1,125 @@
+// NOTE: Assertions have been autogenerated by utils/update_cc_test_checks.py
UTC_ARGS: --function-signature
+// RUN: %clang_cc1 -triple wasm64-unknown-unknown -o - -emit-llvm %s |
FileCheck %s
+
+#include <stdarg.h>
+
+// CHECK-LABEL: define {{[^@]+}}@test_i32
+// CHECK-SAME: (ptr noundef [[FMT:%.*]], ...) #[[ATTR0:[0-9]+]] {
+// CHECK-NEXT: entry:
+// CHECK-NEXT: [[FMT_ADDR:%.*]] = alloca ptr, align 8
+// CHECK-NEXT: [[VA:%.*]] = alloca ptr, align 8
+// CHECK-NEXT: [[V:%.*]] = alloca i32, align 4
----------------
folkertdev wrote:
this is fine, it's saying that there is some `i32` value on the stack, and that
stack allocation has an alignment of 4 (which is appropriate for a 32-bit
integer).
What you're aiming to change here is the alignment in the variable argument
list, which is not observable when reading just a single variadic argument.
https://github.com/llvm/llvm-project/pull/173580
_______________________________________________
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
