public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Thomas Schwinge <tschwinge@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc/devel/rust/master] Merge #1435 Date: Sat, 6 Aug 2022 12:10:36 +0000 (GMT) [thread overview] Message-ID: <20220806121036.5103A3858C2F@sourceware.org> (raw) https://gcc.gnu.org/g:8725e324aad3eac0df074e5f0a494b5e3f332a31 commit 8725e324aad3eac0df074e5f0a494b5e3f332a31 Merge: a39108dea1d f70783d0633 Author: bors[bot] <26634292+bors[bot]@users.noreply.github.com> Date: Fri Aug 5 12:42:24 2022 +0000 Merge #1435 1435: Update the type hasher to stop duplication of aggregate types r=philberty a=philberty The hasher we ported was always calling TYPE_HASH which ends up with DECL_UID which is geneated causing aggregate types keep having a unique hash which ends up confusing the middle end as two copy's of the same aggegate type ends up making GCC think there is some kind of type conversion required here. Fixes #1434 Co-authored-by: Philip Herron <philip.herron@embecosm.com> Diff: gcc/rust/backend/rust-compile-context.cc | 13 ++++-- gcc/testsuite/rust/compile/torture/issue-1434.rs | 53 ++++++++++++++++++++++++ 2 files changed, 63 insertions(+), 3 deletions(-)
reply other threads:[~2022-08-06 12:10 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220806121036.5103A3858C2F@sourceware.org \ --to=tschwinge@gcc.gnu.org \ --cc=gcc-cvs@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).