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 #1281 #1282 Date: Wed, 8 Jun 2022 12:50:40 +0000 (GMT) [thread overview] Message-ID: <20220608125040.02D1F388B585@sourceware.org> (raw) https://gcc.gnu.org/g:5c84a5ca514398f858020c378c5a26f0593eaee3 commit 5c84a5ca514398f858020c378c5a26f0593eaee3 Merge: d5c1531cc41 3a95f28788d 56634945fb2 Author: bors[bot] <26634292+bors[bot]@users.noreply.github.com> Date: Thu May 26 08:26:39 2022 +0000 Merge #1281 #1282 1281: Add testcase to prove bug is fixed r=philberty a=philberty This bug was fixed in commit cb4d935508def8b250345ba5205a90ad9e177ab4 with related PR #1223 The issue is that associated types get updated depending on the context they are used so we need to monomorphize the types when we can so that we don't then throw off the rest of type checking with bogus errors like this. Fixes #1237 1282: Add build badges for marks build-farm r=philberty a=philberty Fixes #1236 Co-authored-by: Philip Herron <philip.herron@embecosm.com> Diff: README.md | 9 +++++++++ gcc/testsuite/rust/compile/issue-1237.rs | 23 +++++++++++++++++++++++ 2 files changed, 32 insertions(+)
reply other threads:[~2022-06-08 12:50 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=20220608125040.02D1F388B585@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).