From: ardadem <ardadem@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: mesa: update to 22.3.5.
Date: Tue, 14 Feb 2023 22:10:09 +0100 [thread overview]
Message-ID: <20230214211009.w8u-MLw_YrUkw_cdNcmKH-2EQ1GN0LZ_VzM8eriwZEc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41084@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 666 bytes --]
New comment by ardadem on void-packages repository
https://github.com/void-linux/void-packages/pull/41084#issuecomment-1430381994
Comment:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/7743
It is actually broken but sometimes it is not.
> Given that the commits which (un)break things with LTO tend to be not directly related to any code actually used on the affected setup, there seem to be other bigger factors than the specific commit. I'd say any commit which exists today has to be assumed to be potentially affected.
Anyways, we should keep it disabled.
> Mesa is known to hit various issues with LTO, I'd recommend disabling it for now.
next prev parent reply other threads:[~2023-02-14 21:10 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 13:28 [PR PATCH] mesa: update to 22.3.0 ardadem
2022-12-15 4:49 ` zlice
2022-12-15 5:11 ` [PR PATCH] [Updated] " ardadem
2022-12-15 9:43 ` [PR PATCH] [Updated] mesa: update to 22.3.1 ardadem
2022-12-17 13:42 ` biopsin
2022-12-19 20:32 ` [PR PATCH] [Updated] " ardadem
2022-12-19 20:50 ` ardadem
2022-12-23 19:53 ` bubba-champion
2022-12-23 20:15 ` vincele
2022-12-23 21:54 ` [PR PATCH] [Updated] " ardadem
2022-12-23 21:58 ` ardadem
2022-12-24 17:56 ` bubba-champion
2022-12-24 19:29 ` bubba-champion
2022-12-29 23:07 ` bubba-champion
2022-12-30 9:15 ` [PR PATCH] [Updated] " ardadem
2023-01-03 22:18 ` [PR PATCH] [Updated] mesa: update to 22.3.2 ardadem
2023-01-03 22:19 ` ardadem
2023-01-11 20:13 ` Seltyk
2023-01-11 21:38 ` [PR PATCH] [Updated] " ardadem
2023-01-17 12:02 ` mesa: update to 22.3.3 motorto
2023-01-17 12:03 ` motorto
2023-01-17 12:33 ` JamiKettunen
2023-01-17 12:34 ` JamiKettunen
2023-01-17 13:14 ` JamiKettunen
2023-01-17 13:14 ` JamiKettunen
2023-01-17 17:07 ` [PR PATCH] [Updated] " ardadem
2023-01-17 17:11 ` ardadem
2023-01-17 17:12 ` [PR PATCH] [Updated] " ardadem
2023-01-17 17:46 ` ardadem
2023-01-17 17:47 ` ardadem
2023-01-17 23:12 ` motorto
2023-01-17 23:19 ` ardadem
2023-01-17 23:25 ` motorto
2023-01-18 0:40 ` JamiKettunen
2023-01-21 12:24 ` lemmi
2023-01-24 23:36 ` motorto
2023-01-27 12:10 ` bubba-champion
2023-01-27 16:53 ` [PR PATCH] [Updated] " ardadem
2023-01-28 4:55 ` mesa: update to 22.3.4 HadetTheUndying
2023-01-28 8:41 ` ardadem
2023-01-28 9:11 ` [PR PATCH] [Updated] " ardadem
2023-01-28 9:14 ` ardadem
2023-01-28 10:13 ` bubba-champion
2023-01-28 12:20 ` motorto
2023-01-28 18:41 ` HadetTheUndying
2023-01-31 22:14 ` Piraty
2023-01-31 22:15 ` Piraty
2023-02-01 0:36 ` HadetTheUndying
2023-02-02 16:03 ` bubba-champion
2023-02-08 20:48 ` HadetTheUndying
2023-02-10 12:44 ` bubba-champion
2023-02-14 9:21 ` [PR PATCH] [Updated] " ardadem
2023-02-14 12:02 ` mesa: update to 22.3.5 motorto
2023-02-14 20:56 ` ardadem
2023-02-14 21:09 ` ardadem
2023-02-14 21:10 ` ardadem [this message]
2023-02-19 17:33 ` [PR PATCH] [Updated] " ardadem
2023-02-19 17:36 ` ardadem
2023-02-21 8:43 ` [PR PATCH] [Closed]: " Piraty
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=20230214211009.w8u-MLw_YrUkw_cdNcmKH-2EQ1GN0LZ_VzM8eriwZEc@z \
--to=ardadem@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).