public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.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: Wed, 26 Aug 2020 08:04:47 +0000 [thread overview] Message-ID: <bug-96153-4-Mq70pPGcJP@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 #8 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Iain Buclaw <ibuclaw@gcc.gnu.org>: https://gcc.gnu.org/g:1db88844a22f75b13ced224415f645680784d354 commit r11-2864-g1db88844a22f75b13ced224415f645680784d354 Author: Iain Buclaw <ibuclaw@gdcproject.org> Date: Tue Aug 25 11:05:57 2020 +0200 d: Fix small struct literals that have non-deterministic hash values Same issue as the initial commit that addressed PR96153, only this time to fix it also for structs that are not returned in memory. Tests have been added that triggered an assertion on x86_64, however the original test was failing on SPARC 64-bit targets. gcc/d/ChangeLog: PR d/96153 * d-codegen.cc (build_address): Create a temporary for CALL_EXPRs returning trivial aggregates, pre-filling it with zeroes. (build_memset_call): Use build_zero_cst if setting the entire object. gcc/testsuite/ChangeLog: PR d/96153 * gdc.dg/pr96153.d: Add new tests.
next prev parent reply other threads:[~2020-08-26 8:04 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 2020-08-24 19:49 ` ibuclaw at gdcproject dot org 2020-08-26 8:04 ` cvs-commit at gcc dot gnu.org [this message] 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-Mq70pPGcJP@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).