Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Review Suggested Edit

You can't approve or reject suggested edits because you haven't yet earned the Edit Posts ability.

typeof_unqual behaves differently in gcc and clang

~~C23 6.7.3.6 contains this (informative) example demonstating the use of `typeof_unqual`:~~
```c
const char* const animals[] = {
"aardvark",
"bluejay",
"catte",
};
typeof_unqual(animals) animals2_array[3];
```
And this is supposedly equivalent to `const char* animals2_array[3];` according to the example. That is also the result I get from clang 19.1.
But in gcc 14.2 I get the type `const char* const [3]`.
Full example: https://godbolt.org/z/Gf9M43nrM
What is correct? Is the standard unclear? The parts about `typeof_unqual` in 6.7.3.6 do not mention arrays at all.

C23 6.7.3.6 contains this (informative) example demonstrating the use of `typeof_unqual`:
```c
const char* const animals[] = {
"aardvark",
"bluejay",
"catte",
};
typeof_unqual(animals) animals2_array[3];
```
And this is supposedly equivalent to `const char* animals2_array[3];` according to the example. That is also the result I get from clang 19.1.
But in gcc 14.2 I get the type `const char* const [3]`.
Full example: https://godbolt.org/z/Gf9M43nrM
What is correct? Is the standard unclear? The parts about `typeof_unqual` in 6.7.3.6 do not mention arrays at all.

c gcc clang c23 typeof

Communities

Review Suggested Edit