Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

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.

Post History

66%
+2 −0
Q&A typeof_unqual behaves differently in gcc and clang

C23 6.7.3.6 contains this (informative) example demonstrating the use of typeof_unqual: const char* const animals[] = { "aardvark", "bluejay", "catte", }; typeof_unqual(animals) anima...

1 answer  ·  posted 16d ago by Lundin‭  ·  edited 16d ago by hkotsubo‭

Question c gcc clang c23 typeof
#2: Post edited by user avatar hkotsubo‭ · 2024-11-26T13:00:59Z (16 days ago)
fix typo
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.
#1: Initial revision by user avatar Lundin‭ · 2024-11-26T11:56:38Z (16 days ago)
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.