From: voidbert <voidbert@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Updating Zig to 0.11.0
Date: Sun, 13 Aug 2023 17:41:27 +0200 [thread overview]
Message-ID: <20230813154127._3johteSIre2oeA90-53VDikgujay052t1SGQ6hWeqk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45424@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 542 bytes --]
New comment by voidbert on void-packages repository
https://github.com/void-linux/void-packages/issues/45424#issuecomment-1676395432
Comment:
@icp1994 The best strategy would be for the folks at LLVM to make their software backwards / forwards compatible, but we all know that's not gonna happen. Nevertheless, Zig will be coming out with some alternative backends (C, x86, ARM and LLVM bitcode, instead of linking to LLVM libraries). This would remove the mandatory LLVM dependency, making a zig update just a version bump + new checksum.
next prev parent reply other threads:[~2023-08-13 15:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 17:17 [ISSUE] " booniepepper
2023-08-04 17:38 ` booniepepper
2023-08-04 18:59 ` icp1994
2023-08-04 20:29 ` booniepepper
2023-08-13 11:56 ` voidbert
2023-08-13 14:02 ` icp1994
2023-08-13 15:41 ` voidbert [this message]
2023-08-13 15:46 ` booniepepper
2023-08-13 15:57 ` voidbert
2023-08-13 17:55 ` booniepepper
2023-08-14 9:54 ` tranzystorek-io
2023-10-10 17:26 ` Anachron
2023-10-10 22:22 ` voidbert
2023-10-10 23:54 ` booniepepper
2023-10-11 5:46 ` Anachron
2024-01-10 1:47 ` github-actions
2024-01-10 9:10 ` booniepepper
2024-02-09 17:35 ` icp1994
2024-02-09 17:37 ` tranzystorekk
2024-02-09 18:58 ` icp1994
2024-02-10 12:42 ` Anachron
2024-02-11 20:49 ` voidbert
2024-02-12 3:59 ` Calandracas606
2024-02-12 4:46 ` Anachron
2024-05-13 1:46 ` github-actions
2024-05-27 1:47 ` [ISSUE] [CLOSED] " github-actions
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=20230813154127._3johteSIre2oeA90-53VDikgujay052t1SGQ6hWeqk@z \
--to=voidbert@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).