Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(88)

Unified Diff: tests_lit/parse_errs/call-fcn-bad-param-type.ll

Issue 1354673002: Fix call instructions to check parameter types for consistency. (Closed) Base URL: https://chromium.googlesource.com/native_client/pnacl-subzero.git@master
Patch Set: Fix minimal build to work. Created 5 years, 3 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: tests_lit/parse_errs/call-fcn-bad-param-type.ll
diff --git a/tests_lit/parse_errs/call-fcn-bad-param-type.ll b/tests_lit/parse_errs/call-fcn-bad-param-type.ll
new file mode 100644
index 0000000000000000000000000000000000000000..96649ef57f553d8aa337d19f104cc3e0b70340c0
--- /dev/null
+++ b/tests_lit/parse_errs/call-fcn-bad-param-type.ll
@@ -0,0 +1,13 @@
+; Test that even in a call parameter matches its declaration, it must still
Jim Stichnoth 2015/09/17 19:56:46 even if
Karl 2015/09/18 17:22:49 Done.
+; be a legal call parameter type (unless declaration is intrinsic).
+
+; RUN: %p2i --expect-fail -i %s --insts | FileCheck %s
+
+declare void @f(i8);
+
+define void @Test() {
+entry:
+ call void @f(i8 1)
+; CHECK: Call argument 1 matches declaration but has invalid type: i8
+ ret void
+}

Powered by Google App Engine
This is Rietveld 408576698