Bug 71713 - "initializer element is not constant" with nested casts
Summary: "initializer element is not constant" with nested casts
Status: NEW
Alias: None
Product: gcc
Classification: Unclassified
Component: c (show other bugs)
Version: 6.1.1
: P3 enhancement
Target Milestone: ---
Assignee: Not yet assigned to anyone
Keywords: rejects-valid
Depends on:
Reported: 2016-06-30 12:52 UTC by vicencb
Modified: 2021-09-19 23:52 UTC (History)
2 users (show)

See Also:
Known to work:
Known to fail:
Last reconfirmed: 2021-09-19 00:00:00


Note You need to log in before you can comment on or make changes to this bug.
Description vicencb 2016-06-30 12:52:47 UTC

With this type definitions:
 struct Str1 { int i; };
 struct Str2 { struct Str1 *m; };

Gcc fails to compile this:
 const struct Str2 cnt = { .m = (struct Str1[]){
  (struct Str1){1}
Reporting "error: initializer element is not constant"

If the inner cast is removed:
 const struct Str2 cnt = { .m = (struct Str1[]){
Then it works fine.

As a side note, clang accepts it.

Comment 1 Martin Sebor 2016-07-01 22:39:46 UTC
I believe the error is justified because a compound literal (i.e., "(struct Str1){1}") is not a constant expression, and so it cannot be used to initialize an object with static storage duration.  GCC accepts compound literals as initializers in some contexts as an extension but not here.  For instance, the following is accepted but in pedantic mode diagnosed with

  struct Str1 x = (struct Str1){ 0 };

  warning: initializer element is not constant [-Wpedantic]

...but it doesn't accept the more involved initializer in the submitted test case.  Since there are a number of enhancement requests to change GCC to accept more expressions as initializers that aren't constant expressions (for example, bug 53091) I will confirm this as such.