From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: llvm9: add fixes for the powerpc backend (prepare for rust 1.39 switch to llvm9)
Date: Tue, 05 Nov 2019 13:30:58 +0100 [thread overview]
Message-ID: <20191105123058.HC8qik9Z4lJQDeiB9frywmvHY_dd7wj7KZoxbTNOwms@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-16132@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 486 bytes --]
There's a merged pull request on the void-packages repository
llvm9: add fixes for the powerpc backend (prepare for rust 1.39 switch to llvm9)
https://github.com/void-linux/void-packages/pull/16132
Description:
This fixes Rust with llvm9 on ppc32, so that we can finally switch to it (`llvm-006-bigpic.patch`) - previously it would emit wrong executables that segfault.
While at it, I'm adding an upstream backport that fixes incorrect codegen for certain things such as Chromium.
prev parent reply other threads:[~2019-11-05 12:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 1:02 [PR PATCH] " voidlinux-github
2019-11-05 12:30 ` voidlinux-github [this message]
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=20191105123058.HC8qik9Z4lJQDeiB9frywmvHY_dd7wj7KZoxbTNOwms@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).