all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: Brendan Tildesley <mail@brendan.scot>, 35575@debbugs.gnu.org
Subject: bug#35575: logo,Some graphical programs borked with Guix on Arch
Date: Tue, 31 Mar 2020 16:53:34 +0200	[thread overview]
Message-ID: <87v9mktw29.fsf@devup.no> (raw)
In-Reply-To: <adaf110a-cf9a-4df5-b27a-f119a73f9b95@brendan.scot>

[-- Attachment #1: Type: text/plain, Size: 1311 bytes --]

Brendan Tildesley <mail@brendan.scot> writes:

> To follow up on this old bug, I believe the issue may come from here: 
> https://gitlab.freedesktop.org/mesa/mesa/-/blob/master/src/compiler/glsl/shader_cache.cpp#L144
>
> Mesa calculates a sha1 based on some things they reason affect the 
> output, but likely it is not truely a function of every parameter than 
> can make a difference to the shader output. When we updated from llvm6 
> to lvm7 I'm guessing it changed the shaders somehow, and the llvm 
> version is not included in the hash. Since I have zero understanding 
> mesa, I'm not capable of determining the best solution. One thought is 
> that if we included the mesa /gnu/store path in the calculation, this 
> would make the hash's truely unique for a given mesa version, but also 
> cached shaders that /would/ work would be routinely discarded after an 
> update (i assume?). Would this be sensible or completely break something 
> else? Should we just add the llvm version, or just start a mesa bug 
> report asking for input?

Is this still relevant?  I haven't heard reports about this in a long
time, nor experienced it (anymore) on my super-experimental systems that
switch LLVM and Mesa versions all the time.  So I think the issue might
have been fixed upstream?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2020-03-31 14:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-05  7:58 bug#35575: Some graphical programs borked with Guix on Arch Brendan Tildesley
2019-05-05 10:33 ` Boris A. Dekshteyn
2019-05-07 11:09 ` Brendan Tildesley
2019-05-08  9:42   ` Boris A. Dekshteyn
2020-03-29  4:00 ` bug#35575: logo,Some " Brendan Tildesley
2020-03-31 14:53   ` Marius Bakke [this message]
2021-02-22  8:31     ` bug#35575: closing. bug has not reoccurred since Brendan Tildesley

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=87v9mktw29.fsf@devup.no \
    --to=mbakke@fastmail.com \
    --cc=35575@debbugs.gnu.org \
    --cc=mail@brendan.scot \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.