From: oreo639 <oreo639@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [WIP] LLVM 15
Date: Fri, 10 Feb 2023 15:55:04 +0100 [thread overview]
Message-ID: <20230210145504.gp-0UndlJjq4AjsrOiqZ7uBj7i-oOnZy3FOlz9qfaV4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40821@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 816 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/pull/40821#issuecomment-1425912418
Comment:
> libclc (tests fail with unresolved calls https://gist.githubusercontent.com/tranzystorek-io/a2aa8a0d8010af5299f7d1ff9f82c22b/raw/6d316d99d6079990b73ae77d274dd120b9560589/LastTest.log)
The clspv libclc tests fail on every distro afaict (at least on Fedora and Alpine) LLVM upstream's CI compiles with everything enabled except clspv and doesn't run those tests. We don't ship clspv so it should be fine to just disable it.
https://src.fedoraproject.org/rpms/libclc/blob/rawhide/f/libclc.spec#_83
https://github.com/alpinelinux/aports/blob/master/testing/libclc/APKBUILD#L25
https://github.com/llvm/llvm-project/blob/main/.github/workflows/llvm-project-tests.yml#L93
next prev parent reply other threads:[~2023-02-10 14:55 UTC|newest]
Thread overview: 96+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 15:30 [PR PATCH] " tranzystorek-io
2022-11-28 15:32 ` tranzystorek-io
2022-11-28 16:36 ` dkwo
2022-11-28 19:13 ` [PR PATCH] [Updated] " tranzystorek-io
2022-11-28 23:49 ` tranzystorek-io
2022-11-29 0:31 ` tranzystorek-io
2022-12-05 8:05 ` tranzystorek-io
2022-12-05 8:17 ` tranzystorek-io
2022-12-05 8:22 ` [PR REVIEW] " oreo639
2022-12-05 8:22 ` oreo639
2022-12-05 8:29 ` oreo639
2022-12-05 8:29 ` oreo639
2022-12-05 8:30 ` oreo639
2022-12-05 8:39 ` oreo639
2022-12-05 9:28 ` oreo639
2022-12-05 9:55 ` oreo639
2022-12-05 9:55 ` oreo639
2022-12-06 10:11 ` [PR PATCH] [Updated] " tranzystorek-io
2022-12-07 5:04 ` Vaelatern
2022-12-07 5:04 ` Vaelatern
2022-12-12 18:26 ` [PR PATCH] [Updated] " tranzystorek-io
2022-12-17 8:56 ` tranzystorek-io
2022-12-17 9:00 ` tranzystorek-io
2022-12-17 9:09 ` tranzystorek-io
2022-12-17 10:44 ` [PR REVIEW] " paper42
2022-12-17 23:41 ` [PR PATCH] [Updated] " tranzystorek-io
2022-12-18 0:02 ` [PR REVIEW] " oreo639
2022-12-18 0:03 ` oreo639
2022-12-18 0:05 ` oreo639
2022-12-18 11:24 ` [PR PATCH] [Updated] " tranzystorek-io
2022-12-18 23:30 ` tranzystorek-io
2022-12-19 23:58 ` oreo639
2022-12-19 23:59 ` oreo639
2022-12-20 0:04 ` oreo639
2022-12-20 0:09 ` oreo639
2022-12-22 4:26 ` simvux
2022-12-22 4:48 ` oreo639
2022-12-22 10:15 ` ardadem
2023-01-05 14:13 ` [PR PATCH] [Updated] " tranzystorek-io
2023-01-06 12:39 ` [PR REVIEW] " tranzystorek-io
2023-01-06 12:56 ` [PR PATCH] [Updated] " tranzystorek-io
2023-01-06 16:15 ` tranzystorek-io
2023-01-07 10:31 ` tranzystorek-io
2023-01-07 17:02 ` tranzystorek-io
2023-01-09 0:22 ` tranzystorek-io
2023-01-09 0:58 ` tranzystorek-io
2023-01-10 8:20 ` dkwo
2023-01-12 18:46 ` [PR PATCH] [Updated] " tranzystorek-io
2023-01-14 22:16 ` Johnnynator
2023-01-15 1:46 ` [PR PATCH] [Updated] " tranzystorek-io
2023-01-16 13:45 ` tranzystorek-io
2023-01-17 19:01 ` [PR REVIEW] " Johnnynator
2023-01-24 13:05 ` [PR PATCH] [Updated] " tranzystorek-io
2023-01-24 13:15 ` tranzystorek-io
2023-01-26 22:36 ` tranzystorek-io
2023-02-01 12:34 ` tranzystorek-io
2023-02-05 12:42 ` tranzystorek-io
2023-02-05 13:58 ` tranzystorek-io
2023-02-07 9:14 ` tranzystorek-io
2023-02-10 14:20 ` tranzystorek-io
2023-02-10 14:49 ` oreo639
2023-02-10 14:50 ` oreo639
2023-02-10 14:51 ` oreo639
2023-02-10 14:51 ` oreo639
2023-02-10 14:55 ` oreo639 [this message]
2023-02-10 16:26 ` [PR PATCH] [Updated] " tranzystorek-io
2023-02-10 16:42 ` tranzystorek-io
2023-02-10 19:21 ` tranzystorek-io
2023-02-15 17:27 ` tranzystorek-io
2023-02-16 19:17 ` tranzystorek-io
2023-02-16 22:44 ` tranzystorek-io
2023-02-18 19:34 ` tranzystorek-io
2023-02-19 22:34 ` simvux
2023-02-20 9:59 ` cmueller-tp
2023-02-22 12:35 ` [PR PATCH] [Updated] " tranzystorek-io
2023-02-22 14:35 ` tranzystorek-io
2023-02-22 19:26 ` tranzystorek-io
2023-02-22 19:41 ` [PR PATCH] [Updated] " tranzystorek-io
2023-02-24 22:55 ` Johnnynator
2023-03-01 14:02 ` [PR PATCH] [Updated] " tranzystorek-io
2023-03-10 14:35 ` tranzystorek-io
2023-03-13 14:25 ` motorto
2023-03-13 14:27 ` tranzystorek-io
2023-03-18 3:31 ` ihameed
2023-03-18 3:39 ` ihameed
2023-03-18 4:46 ` ihameed
2023-03-18 9:35 ` [PR PATCH] [Updated] " tranzystorek-io
2023-03-18 16:35 ` tranzystorek-io
2023-03-25 6:04 ` oreo639
2023-03-25 13:04 ` [PR PATCH] [Updated] " tranzystorek-io
2023-03-25 13:10 ` tranzystorek-io
2023-03-30 22:02 ` tranzystorek-io
2023-03-31 13:28 ` [PR PATCH] [Closed]: " leahneukirchen
2023-04-02 12:17 ` simvux
2023-04-02 12:18 ` tranzystorek-io
2023-04-02 12:19 ` simvux
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=20230210145504.gp-0UndlJjq4AjsrOiqZ7uBj7i-oOnZy3FOlz9qfaV4@z \
--to=oreo639@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).