The initial commit that added opaque types thought that there couldn't
be any valid initializations for variables of these types, but the test
case in the bug report shows that isn't true. The solution is to handle
OPAQUE_TYPE initializations like the other scalar types.
2022-06-17 Peter Bergner <bergner@linux.ibm.com>
gcc/
PR c/106016
* expr.cc (count_type_elements): Handle OPAQUE_TYPE.
gcc/testsuite/
PR c/106016
* gcc.target/powerpc/pr106016.c: New test.
(cherry picked from commit
975658b782f36dcf6eb190966d5b705977bfd5eb)
case OFFSET_TYPE:
case REFERENCE_TYPE:
case NULLPTR_TYPE:
+ case OPAQUE_TYPE:
return 1;
case ERROR_MARK:
return 0;
case VOID_TYPE:
- case OPAQUE_TYPE:
case METHOD_TYPE:
case FUNCTION_TYPE:
case LANG_TYPE:
--- /dev/null
+/* PR target/106016 */
+/* { dg-require-effective-target power10_ok } */
+/* { dg-options "-O2 -mdejagnu-cpu=power10" } */
+
+/* Make sure we do not ICE on the following test case. */
+
+extern void bar (__vector_quad *);
+
+void
+foo (__vector_quad *a, __vector_quad *b)
+{
+ __vector_quad arr[2] = {*a, *b};
+ bar (&arr[0]);
+}