Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: Package Request: GCC 9.1
Date: Mon, 03 Jun 2019 16:50:33 +0200	[thread overview]
Message-ID: <20190603145033.nFnqrrxbe34h5UKZXEOL1XiLvPAWw5KkqVkPl4FdIHQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-11663@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1159 bytes --]

New comment by pullmoll on void-packages repository

https://github.com/void-linux/void-packages/issues/11663#issuecomment-493716506
Comment:
An interesting answer related to the question whether unnamed struct members are initialized can be found here https://stackoverflow.com/questions/330793/ in the comment https://stackoverflow.com/a/37701574/

Specifically ISO/IEC 9899:2011 and ISO/IEC 9899:2018 are said to retain the paragraph 9 statement:

> Except where explicitly stated otherwise, for the purposes of this subclause unnamed members of objects of structure and union type do not participate in initialization. **Unnamed members of structure objects have indeterminate value even after initialization.**

So if gcc9 implemented ISO/IEC 9899:2011 and ISO/IEC 9899:2018 verbatim one would hope the https://gcc.gnu.org/onlinedocs/gcc/Designated-Inits.html statement

> Omitted field members are implicitly initialized the same as objects that have static storage duration.

still holds true. Other C99 compliant compilers may not initialize the unnamed struct members as gcc8 did and, let's hope, gcc9 still does. If gcc9 does not, well...

  parent reply	other threads:[~2019-06-03 14:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-11663@inbox.vuxu.org>
2019-06-03 14:48 ` voidlinux-github
2019-06-03 14:48 ` voidlinux-github
2019-06-03 14:50 ` voidlinux-github [this message]
2019-06-03 14:50 ` voidlinux-github
2019-06-03 15:01 ` voidlinux-github
2019-06-03 23:44 ` voidlinux-github
2019-06-03 23:44 ` voidlinux-github
2019-06-19 19:01 ` voidlinux-github
2019-06-20 13:58 ` voidlinux-github
2019-06-27 11:14 ` [ISSUE] [CLOSED] " voidlinux-github
2019-06-28 14:13 ` voidlinux-github

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=20190603145033.nFnqrrxbe34h5UKZXEOL1XiLvPAWw5KkqVkPl4FdIHQ@z \
    --to=voidlinux-github@inbox.vuxu.org \
    --cc=ml@inbox.vuxu.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: link
Be 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 NNTP newsgroup(s).