https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120510
Bug ID: 120510
Summary: composite_type produces result not compatible with
arguments
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: minor
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: uecker at gcc dot gnu.org
Target Milestone: ---
composite_type can produce results which are not compatible with its arguments
dues to mismatch qualifiers as judged by comptypes (as seen when adding such
tests as assertions). This may be because we call it incorrectly or perhaps
because of a bug in composite_type. I am not sure whether this can lead to a
user-visible defect.
Two examples are:
const char z[1][1];
char x[1][1];
void f()
{
x == z;
}
------------------------
int foo(int i[_Atomic]);
int foo(int i[_Atomic]);
This came up on the ML:
https://gcc.gnu.org/pipermail/gcc-patches/2025-June/685365.html
