public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/105430] New: [11/12/13 Regression] [DR 413] Change in value for "Partial overriding of constant struct/union initializers with designated initializers" Date: Fri, 29 Apr 2022 00:20:50 +0000 [thread overview] Message-ID: <bug-105430-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105430 Bug ID: 105430 Summary: [11/12/13 Regression] [DR 413] Change in value for "Partial overriding of constant struct/union initializers with designated initializers" Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: hp at gcc dot gnu.org Target Milestone: --- Created attachment 52902 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52902&action=edit test-case This bug is different to PR63944 where the description says "This bug is specific to initializers of objects with automatic storage duration" but where comments mention problems with static duration, so it's apparently part of a set of related problems or same base problem: here we have a constant static object. Also, part of this sub-problem is that the initialized value changed between gcc-10 and gcc-11, which does not appear to be the case for the code in PR63944. The test-case in this PR shows a regression since gcc-10 (and earlier releasess) behaves correctly; only the overridden field changed value, as intended. It manifests for all targets.
next reply other threads:[~2022-04-29 0:20 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-29 0:20 hp at gcc dot gnu.org [this message] 2022-04-29 0:25 ` [Bug c/105430] " pinskia at gcc dot gnu.org 2022-04-29 6:40 ` rguenth at gcc dot gnu.org 2022-07-26 11:43 ` rguenth at gcc dot gnu.org 2023-05-29 10:06 ` [Bug c/105430] [11/12/13/14 " jakub at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-105430-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).