From: motorto <motorto@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] Llvm13
Date: Sat, 19 Mar 2022 20:58:23 +0100 [thread overview]
Message-ID: <20220319195823.x_FBl5BHrTPRQl2loiRgwZ0fyuyGPTmBEl5qyAhWbjM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35895@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1046 bytes --]
There is an updated pull request by motorto against master on the void-packages repository
https://github.com/motorto/void-packages llvm13
https://github.com/void-linux/void-packages/pull/35895
Llvm13
This adds LLVM 13 and updates from LLVM 12.
Work-in-progress
The following packages were removed:
* beignet -- upstream is dead
* rundird -- has been deprecated by upstream which recommends using dumb_runtime_dir
The following packages were updated or patched:
* ispc
* qtcreator
* river
* zig
Rebuilt packages:
(rebuilt based on output of: `xrevshlib libllvm{12,13}` )
* SPIRV-LLVM-Translator
* bcc
* bpftrace
* ccls
* clazy
* codelite
* ghdl
* gnome-builder
* include-what-you-use
* juCi++
* kdevelop
* ldc
* mesa
* qt5
* rtags
* rust
* shiboken2
* tilix
Updated Templates:
* Chromium
(I am probably missing some packages)
Thanks @DBLouis for your hard work!
[ci skip]
A patch file from https://github.com/void-linux/void-packages/pull/35895.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-llvm13-35895.patch --]
[-- Type: text/x-diff, Size: 0 bytes --]
next prev parent reply other threads:[~2022-03-19 19:58 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 21:56 [PR PATCH] Llvm13 motorto
2022-02-28 22:04 ` [PR PATCH] [Updated] Llvm13 motorto
2022-02-28 22:12 ` motorto
2022-03-02 11:57 ` Llvm13 ifreund
2022-03-02 20:22 ` Llvm13 ifreund
2022-03-02 20:24 ` Llvm13 ifreund
2022-03-02 20:25 ` Llvm13 ifreund
2022-03-02 20:50 ` [PR PATCH] [Updated] Llvm13 motorto
2022-03-02 20:54 ` motorto
2022-03-02 21:01 ` motorto
2022-03-02 21:12 ` motorto
2022-03-03 18:27 ` Llvm13 Johnnynator
2022-03-04 12:06 ` Llvm13 motorto
2022-03-04 12:06 ` [PR PATCH] [Updated] Llvm13 motorto
2022-03-04 12:09 ` motorto
2022-03-04 12:17 ` motorto
2022-03-04 12:18 ` Llvm13 motorto
2022-03-04 16:58 ` [PR PATCH] [Updated] Llvm13 motorto
2022-03-04 17:00 ` motorto
2022-03-04 18:12 ` motorto
2022-03-04 18:19 ` motorto
2022-03-05 11:59 ` motorto
2022-03-17 15:00 ` Llvm13 dkwo
2022-03-19 19:58 ` [PR PATCH] [Closed]: Llvm13 motorto
2022-03-19 19:58 ` motorto [this message]
2022-03-19 20:13 ` Llvm13 motorto
2022-03-29 14:00 ` Llvm13 subnut
2022-03-29 14:01 ` Llvm13 subnut
2022-03-29 14:02 ` Llvm13 subnut
2022-03-19 20:12 [PR PATCH] Llvm13 motorto
2022-03-29 8:28 ` [PR PATCH] [Updated] Llvm13 motorto
2022-03-30 20:48 ` motorto
2022-03-30 20:50 ` motorto
2022-03-30 20:51 ` motorto
2022-03-31 6:20 ` motorto
2022-03-31 16:03 ` motorto
2022-03-31 18:55 ` motorto
2022-03-31 21:16 ` motorto
2022-04-01 8:36 ` motorto
2022-05-22 8:58 ` motorto
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=20220319195823.x_FBl5BHrTPRQl2loiRgwZ0fyuyGPTmBEl5qyAhWbjM@z \
--to=motorto@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).