From: non-Jedi <non-Jedi@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: julia: update to 1.5.0.
Date: Wed, 26 Aug 2020 04:46:07 +0200 [thread overview]
Message-ID: <20200826024607.Tikn4TvHGyLIN0Vss_5j4usHyiwafhdGSWlofxDh9J8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24097@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 652 bytes --]
New comment by non-Jedi on void-packages repository
https://github.com/void-linux/void-packages/pull/24097#issuecomment-680440017
Comment:
I'll build overnight and take a look tomorrow. I would certainly hope that julia would include tests for whatever issues their llvm patches address, but I'm not very confident that's the case, so I'll also dig through the julia repo's git blame and see if I can reproduce whatever issues the patches are for (and whether those issues are significant in practice). llvm10 is not officially supported by julia, so at the very least we may want to build against llvm9 (assuming the test suite is similarly clean).
next prev parent reply other threads:[~2020-08-26 2:46 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-06 2:50 [PR PATCH] " non-Jedi
2020-08-06 14:12 ` non-Jedi
2020-08-06 21:39 ` [PR PATCH] [Updated] " non-Jedi
2020-08-06 21:41 ` non-Jedi
2020-08-24 2:17 ` rjpower4
2020-08-24 18:41 ` non-Jedi
2020-08-25 14:56 ` ahesford
2020-08-25 15:01 ` [PR REVIEW] " ahesford
2020-08-25 15:25 ` ericonr
2020-08-25 16:33 ` [PR REVIEW] " non-Jedi
2020-08-25 19:22 ` [PR PATCH] [Updated] " ahesford
2020-08-25 19:26 ` ahesford
2020-08-25 19:53 ` [PR REVIEW] " non-Jedi
2020-08-25 19:53 ` non-Jedi
2020-08-25 19:53 ` non-Jedi
2020-08-25 19:56 ` non-Jedi
2020-08-25 19:59 ` non-Jedi
2020-08-25 20:00 ` non-Jedi
2020-08-25 20:04 ` ahesford
2020-08-25 20:05 ` ahesford
2020-08-25 20:09 ` ahesford
2020-08-25 20:09 ` ahesford
2020-08-25 20:18 ` non-Jedi
2020-08-25 20:20 ` non-Jedi
2020-08-25 20:21 ` non-Jedi
2020-08-25 20:29 ` non-Jedi
2020-08-25 20:47 ` ahesford
2020-08-25 21:32 ` [PR PATCH] [Updated] " ahesford
2020-08-25 21:33 ` ahesford
2020-08-26 1:58 ` [PR PATCH] [Updated] " non-Jedi
2020-08-26 2:00 ` non-Jedi
2020-08-26 2:03 ` [PR REVIEW] " non-Jedi
2020-08-26 2:14 ` non-Jedi
2020-08-26 2:30 ` [PR PATCH] [Updated] " ahesford
2020-08-26 2:30 ` ahesford
2020-08-26 2:44 ` [PR REVIEW] " ahesford
2020-08-26 2:46 ` non-Jedi [this message]
2020-08-26 2:52 ` ahesford
2020-08-26 2:56 ` non-Jedi
2020-08-26 2:57 ` non-Jedi
2020-08-26 4:06 ` [PR PATCH] [Closed]: " ahesford
2020-08-26 4:09 ` ahesford
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=20200826024607.Tikn4TvHGyLIN0Vss_5j4usHyiwafhdGSWlofxDh9J8@z \
--to=non-jedi@users.noreply.github.com \
--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).