================
@@ -91,7 +91,8 @@ __externref_t func(__externref_t ref) {
   varargs(1, table);              // expected-error {{cannot use WebAssembly 
table as a function parameter}}
   table == 1;                     // expected-error {{invalid operands to 
binary expression ('__attribute__((address_space(1))) __externref_t[0]' and 
'int')}}
   1 >= table;                     // expected-error {{invalid operands to 
binary expression ('int' and '__attribute__((address_space(1))) 
__externref_t[0]')}}
-  table == other_table;           // expected-error {{invalid operands to 
binary expression ('__attribute__((address_space(1))) __externref_t[0]' and 
'__attribute__((address_space(1))) __externref_t[0]')}}
+  table == other_table;           // expected-error {{invalid operands to 
binary expression ('__attribute__((address_space(1))) __externref_t[0]' and 
'__attribute__((address_space(1))) __externref_t[0]')}} \
----------------
Sirraide wrote:

Is there some way to move the deprecation warning/error check to after we 
diagnose comparison of these WASM types as ill-formed?

https://github.com/llvm/llvm-project/pull/191101
_______________________________________________
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Reply via email to