public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ibuclaw at gdcproject dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/96153] d: struct literals have non-deterministic hash values
Date: Sun, 23 Aug 2020 07:05:53 +0000	[thread overview]
Message-ID: <bug-96153-4-ihyseb15c0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96153-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96153

--- Comment #6 from Iain Buclaw <ibuclaw at gdcproject dot org> ---
The distinction between x86_64 passing and SPARC64 failing seems to be whether
the struct returns in memory, or via registers.  If via registers, alignment
holes that were filled are ignored by the caller (values are copied away from
the returned struct, so holes will not be carried over to the destination).

By that measure then, all initialization of any struct type that doesn't
satisfy identity_compare_p will require pre-filling with zeros.  There are
still some cases where this does not happen, such as in this testcase:
toHash(checked(12));

  parent reply	other threads:[~2020-08-23  7:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-10 14:40 [Bug d/96153] New: " ibuclaw at gdcproject dot org
2020-08-04 15:05 ` [Bug d/96153] " cvs-commit at gcc dot gnu.org
2020-08-05  8:46 ` ro at gcc dot gnu.org
2020-08-05 11:42 ` ibuclaw at gdcproject dot org
2020-08-05 16:30 ` ibuclaw at gdcproject dot org
2020-08-06 12:49 ` ibuclaw at gdcproject dot org
2020-08-23  7:05 ` ibuclaw at gdcproject dot org [this message]
2020-08-24 19:49 ` ibuclaw at gdcproject dot org
2020-08-26  8:04 ` cvs-commit at gcc dot gnu.org
2020-08-26  8:05 ` ibuclaw at gdcproject dot 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-96153-4-ihyseb15c0@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: 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 read-only IMAP folder(s) and NNTP newsgroup(s).