Mostly moved to the place where the sky is blue.
Performance, GPU APIs, multithreading and game engines specialist @siliceum.
Does reverse engineering for fun.
@hexawyz@OlexGameDev Yes, that's the reason. One has thread safe init, the other doesn't. That's mandated by the standard for any static variable in a function/method.
The change is fine to do it if you know it can't race, otherwise could use templated inline global.
One of C++ need to know.
@molecularmusing@SheriefFYI I've been bitten by createfile too... And very often due to bad minifilters from security stuff. But the call itself is slow too even on console (I'd even say especially there)
@noop_dev@matiasgoldberg@NOTimothyLottes I'm not sure I follow exactly but if you can limit the number of things you send with traditional APIs, why can't you do the same with iouring if you need to limit oversubscription? Having bounds for the submitted work is always desirable, be it iouring or not IMHO.
@noop_dev@matiasgoldberg@NOTimothyLottes But it also gives the kernel/driver less control (or at least not for the same price).
The kernel has fastpaths and can usually do things better than us depending on the hardware (notably I/O scheduling). It can still do it without io rings obviously but it's more expensive.
@noop_dev@matiasgoldberg@NOTimothyLottes Except the posix APIs have always been either blocking or fully shit to use async. And async is required if you want proper perf, spinning more threads is not the solution.
There's a reason (as mentioned by the others) drivers and hardware (not just GPUs) use command buffers.
To the fucktard designer at @SamsungMobile or @Android who decided that opening an update dialog under my fingers AT 15% battery WITH A BUTTON AT THE KEYBOARD LOCATION WITHOUT ANY FUCKING CONFIRMATION DIALOG OR GRACE PERIOD:
YOU SHOULD BE FIRED AND EAT MY PHONE
Fuck you very much @Samsung.
I've been postponing the oneui6.1 update for a while, and the dialog asking if I want to do it just popped WHILE I WAS TYPING TEXT.
Result: I pressed "update" unknowingly because the button appeared right under my finger.
I could have lost much
@rfleury@matiasgoldberg Did you start the kernel part?
Cause you'll have to parse (barely documented) text based files instead of proper APIs, for which the content may change whenever. At least you can read the kernel source to figure stuff out but that's not better than what the tool chains have.
@ForrestTheWoods I ended up using zigcc which is the only easily accessed toolchain targeting an old glibc. The fact we still need these kind of things (or go musl, which has its own issue) is sad.
@molecularmusing@SheriefFYI@jbevain Yeah it's something I do a lot too, it could be cached but I guess that some rules could be easily invalidated. Not surprising they didn't optimize it but yeah.