aboutsummaryrefslogtreecommitdiff
path: root/gcc/fortran
diff options
context:
space:
mode:
authorPeter Bergner <bergner@linux.ibm.com>2022-06-17 23:43:23 -0500
committerPeter Bergner <bergner@linux.ibm.com>2022-07-26 10:04:44 -0500
commit975658b782f36dcf6eb190966d5b705977bfd5eb (patch)
tree34cf4546577b46404d91bf0f6c5a969369ee148e /gcc/fortran
parent5b96c823e591980a80481eb3fe72092a6146f742 (diff)
downloadgcc-975658b782f36dcf6eb190966d5b705977bfd5eb.zip
gcc-975658b782f36dcf6eb190966d5b705977bfd5eb.tar.gz
gcc-975658b782f36dcf6eb190966d5b705977bfd5eb.tar.bz2
c: Handle initializations of opaque types [PR106016]
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.
Diffstat (limited to 'gcc/fortran')
0 files changed, 0 insertions, 0 deletions