04:17 dcbaker: DavidHeidelberg: that was a port of something in the auto tools build, I don’t even remember who added it initially, but I remember reading the gcc log for why it was removed, and they basically found that outside a few synthetic benchmarks it either hurt or didn’t help performance, so I’d be inclined to mark the option as deprecated and delete the check
04:17 dcbaker: Which I can send a patch for Monday
05:30 DavidHeidelberg: dcbaker: muy bien, gracias! :)
06:20 dcbaker: DavidHeidelberg: de nada
08:33 colinmarc: something I've wondered about for a while: how does the vsync checkbox in games correspond to actual present modes? Is it FIFO?
08:36 K900: Depends on the game really
08:37 K900: But in most cases it's immediate for vsync off and FIFO/mailbox for vsync on
08:55 Lynne: so any way to debug CS rejection on radv?
08:55 Lynne: I'm not even running a shader anywhere
08:56 Lynne: only a single pipeline barrier
09:05 Lynne: oh no, if I disable host mapped image uploads, its fine
09:06 Lynne: but the code runs on other vendors, validation layers don't complain, and the math all checks out, no overreads are possibly happening
18:44 airlied: Lynne: anything in dmesg?
22:25 Ermine: how do you submit docs updates? Is patch 00 of N is suitable for that?
22:29 heat: wdym
22:33 Ermine: I've heard somewhere that one doesn't just send patches for typos or something like that, and one should send them along with some actual patches
22:54 heat: docs typos i'm sure are fine
22:55 heat: when sending out a patch set, "patch 0" is never an actual patch but the cover letter