<icecream95>
For my previous question about threading with LTO, I just changed the linker flag returned by meson:
<icecream95>
sudo sed -i 's/flto/flto=4/' /path/to/mesonbuild/linkers.py
<icecream95>
Let's see how much memory it ends up using...
stikonas has quit [Remote host closed the connection]
<tlwoerner>
wow! my first time running glmark2 (-es2) on tinker with panfrost :-D
<tlwoerner>
NICE! B)
<tlwoerner>
it even did amazingly well with the "terrain" test, which is usually a killer
<tlwoerner>
regular glmark2 segfaults?
<icecream95>
glmark2 (not -es2) segfaults for me too (at least the last time I tried it...)
megi has quit [Ping timeout: 268 seconds]
stikonas has joined #panfrost
stikonas has quit [Remote host closed the connection]
nerdboy has quit [Ping timeout: 240 seconds]
vstehle has quit [Ping timeout: 240 seconds]
mearon has quit [Ping timeout: 245 seconds]
mearon has joined #panfrost
<alyssa>
that sounds like a bug :v
* alyssa
builds
<alyssa>
tlwoerner: :-D
<alyssa>
icecream95: ....Huh.
<tlwoerner>
also, specifying the --annotate option to glmark2-es2 seems to do wonky things (on the tinker)
<alyssa>
tlwoerner: Wonky how..?
<alyssa>
Seems fine for me here on kevin
<tlwoerner>
my screen goes blank, i just restart the xorg server to recover
<alyssa>
*blinks*
<alyssa>
That is wonky.
<alyssa>
Looking at the segfault now
<alyssa>
Looks like we're missing a gallium callback related to FBOs
<tlwoerner>
hmmm... and, of course, it's doing something different now. when it happened (twice now, once in fullscreen, once not) the output on the console keeps going as if nothing is amiss, but the screen is blank
<alyssa>
Welcome to my life!~
<tlwoerner>
lol
<tlwoerner>
meh, ignore that one too wonky to bother chasing it down
<alyssa>
#0 0x0000000000000000 in ?? ()
<alyssa>
#1 0x0000aaaaaab15bc8 in DepthRenderTarget::setup (
<alyssa>
Not helpful ... more things happen in between!
<tlwoerner>
it's really nice seeing panfrost building "out of the box" and it's really nice fullscreen!
* alyssa
has been using panfrost fulltime for two months now
<HdkR>
nullptr? Sounds like it is a failure on the game's side
<HdkR>
Probably exposed a new extension and the thing is assuming one feature also implies another
<alyssa>
HdkR: In glGenFramebuffers() and glGenerateMipmap()
<alyssa>
so no
<HdkR>
ah, can't tell from that backtrace :P
* alyssa
doesn't really understand mesa/st
<alyssa>
`glGenerateMipmap` should not be crashing
<alyssa>
_mesa_GenerateMipmap isn't being called?
<alyssa>
This shouldn't be possible ...
<alyssa>
Oh agh
<alyssa>
HdkR: If I do MESA_GL_VERSION_OVERRIDE=3.0 it's fine.
<alyssa>
2.1 does the crashy path
<alyssa>
Whaaat.
<HdkR>
Fun stuff
<alyssa>
tlwoerner: As a workaround, set MESA_GL_VERSION_OVERRIDE=3.0 and glmark2 is fine
<tlwoerner>
thanks!
<alyssa>
(looks like a bug in glmark)
<tlwoerner>
in --fullscreen with either glmark2 or glmar2-es2 the "ideas" test is missing its shadows
* alyssa
can
<alyssa>
't reproduce that here
<tlwoerner>
ok
<tlwoerner>
a couple of the mesa_demos programs produce an "illegal instruction" (sigkill), is that panfrost-related?
<tlwoerner>
(oops, sigill)
<HdkR>
disas $pc,+4?
<HdkR>
Could be an assert being hit without a message
<HdkR>
Which would be a `brk #1000` on AArch64
<tlwoerner>
HdkR: this is rk3288
<tlwoerner>
tinkerboard
<icecream95>
While we're on the topic of bugs in glmark2, is anyone going to update the Wayland backend to work on sway?
<HdkR>
ARMv7 would be bkpt then I think
<icecream95>
I think glmark2 uses deprecated stuff in wayland that Sway has already removed
<icecream95>
alyssa: I've been using panfrost fulltime for two months and two weeks now :)
<endrift>
HdkR: ARMv5-ARMv7 have bkpt yes
<HdkR>
endrift: Was a guess because I couldn't remember the exact instruction name :P
<icecream95>
That's why you should create an ARM account under a fake company name (I chose G00gLe) so you can download the ARM arch reference manual. :)
<tomeu>
bbrezillon: that's with 5.5-rc1 plus your patches
<tomeu>
the results vary wildly between the machines: t820 just has the 31 expected fails, t720 has an extra 100 failures, t760 hangs as per above and t860 has a few hundreds extra failures
<tomeu>
abordado: I see the labels in the right-side sidebar, and the possibility to edit them
<bbrezillon>
tomeu: it would be interesting to disable per-FD AS and see if you still have this problem
<tomeu>
let's see if I can reproduce it locally
<robmur01>
abordado: tomeu: I believe labels might only be editable by those with "developer" status
abordado has quit [Read error: Connection reset by peer]
abordado has joined #panfrost
abordado has quit [Read error: Connection reset by peer]
abordado has joined #panfrost
abordado has quit [Read error: Connection reset by peer]
abordado has joined #panfrost
abordado_ has joined #panfrost
abordado_ has quit [Read error: Connection reset by peer]
megi has quit [Ping timeout: 250 seconds]
abordado has quit [Ping timeout: 265 seconds]
<alyssa>
tlwoerner: I suppose that's an assert as HdkR mentioned, yes. I'm working on it :)
<alyssa>
one fix just hit master last night, more to come
<robher>
tomeu: That's always drm-misc-next plus the fixes branches. The problem is fixes (and Linus' tree) are merged into drm-misc-next somewhat adhoc.
<alyssa>
icecream95: Woo!
abordado has joined #panfrost
abordado has quit [Read error: Connection reset by peer]
abordado has joined #panfrost
<alyssa>
abordado: Congrats on your first patch!
abordado has quit [Remote host closed the connection]
abordado has joined #panfrost
abordado has quit [Read error: Connection reset by peer]
<tlwoerner>
it looks like glmark2 has a memory leak, it didn't survive an over-night test
abordado_ has joined #panfrost
<alyssa>
Ruh roh.
<tlwoerner>
it got oom'ed at some point
abordado_ has quit [Read error: Connection reset by peer]
abordado has joined #panfrost
<tlwoerner>
alyssa: the illegal instruction?
<alyssa>
Ye
<tlwoerner>
is there anything i can do to help track it down?
<alyssa>
I mean, a debug build would give you the assertions "properly"
<alyssa>
Otherwise, just lmk which test you're looking at and I'll see what's broken
<alyssa>
but if you build mesa from source, that should be debug by default
<tlwoerner>
a debug build of mesa i assume?
<alyssa>
Mm
<abordado>
alyssa: Thanks!
<tlwoerner>
yes, i use OpenEmbedded
<alyssa>
abordado: Good work, here's to a great v2! Let me know if you have any questions!
<robmur01>
out of curiosity, does GL have bitwise booleans like good ol' Visual Basic then? As a C person I see #2025 and I'm all "but... but... but !(1) == !(2)" :)
<alyssa>
robmur01: Doesn't matter what GL does, so much as what our IR does
<alyssa>
And in our IR, `->invert` just means "do a bitwise complement after"
<alyssa>
so not inherently boolean at all
<alyssa>
maybe I should reserve that for just booleans but it hasn't been necessary
<alyssa>
(Note that Midgard has 0/~0 convention for booleans so that corresponds well)
<robmur01>
thanks - as someone who has barely touched any high-level code in years and has essentially no background in graphics or compilers anyway, I'm finding it fascinating to watch
megi has joined #panfrost
<alyssa>
Note that, while `->saturate`/etc is a real thing in the hardware that Mali can do, `->invert` is not
<alyssa>
I just felt like adding the feature to the IR since it's convenient for a lot of opt passes
<alyssa>
Usually can be optimized out, and if not, well we can do an inot instruction (actually, mali doesn't have an inot, but inor with #0 is canonically inot)
abordado has quit [Quit: Leaving]
abordado has joined #panfrost
abordado_ has joined #panfrost
abordado has quit [Ping timeout: 250 seconds]
guillaume_g has quit [Quit: Konversation terminated!]
fysa has joined #panfrost
guillaume_g has joined #panfrost
fysa has quit [Ping timeout: 245 seconds]
<tomeu>
bbrezillon: alyssa ok, looks like the issues I was chasing were due to state leaks that manifest with the mesa runner because it shuffles
<tomeu>
and we seem to have some problems with jobs that time out
abordado_ has quit [Remote host closed the connection]
<alyssa>
tomeu: Alright.
<alyssa>
which specific issues are these?
<alyssa>
The compiler fixes flake?
yann has quit [Ping timeout: 268 seconds]
karolherbst has quit [Ping timeout: 265 seconds]
nerdboy has quit [Ping timeout: 252 seconds]
raster has quit [Quit: Gettin' stinky!]
karolherbst has joined #panfrost
nerdboy has joined #panfrost
yann has joined #panfrost
indy has quit [Ping timeout: 240 seconds]
indy has joined #panfrost
stikonas has joined #panfrost
jschwart has joined #panfrost
guillaume_g has quit [Quit: Konversation terminated!]
davidlt has quit [Ping timeout: 276 seconds]
robertfoss has quit [Ping timeout: 276 seconds]
robertfoss has joined #panfrost
stikonas_ has joined #panfrost
stikonas has quit [Ping timeout: 246 seconds]
jolan has quit [Quit: leaving]
<steev>
swinging back around.... reading back... spilling fixes... fixed enough to launch X with modesetting? or am i misreading
jolan has joined #panfrost
icecream95 has joined #panfrost
icecream95 has quit [Remote host closed the connection]