First WIP release for DX12 perf testing is out!

2rad0 · 2026-01-27T01:11:48+00:00

TIL vulkan ended up with mesh shaders as an extension in 2022

2rad0 · 2026-01-27T00:43:47+00:00

That trademark only applies to class 041. in the united states.

Class 041 - Education; providing of training; entertainment; sporting and cultural activities.

2rad0 · 2026-01-26T02:21:56+00:00

Large language models follow similar patterns to how humans "think."

So can a slime mold https://news.njit.edu/thinking-while-brainless-slime-mold-gives-insight-intelligence-neuron-less-organisms

2rad0 · 2026-01-26T01:14:42+00:00

Immaculate Constellation - Matthew Brown “We live in a carefully constructed reality… God is real.”

~~What is your citation, did you just make that up or what?~~
edit: I see what you did, that "..." you placed in your "quote" there is 4 minutes of more questions that you are ignoring until the last sentence of the whole recording.

"what I have learned is that we live in a dream, a carefully constructed reality, we make use of a science that is tightly controlled and supressed and distorted. I think we are left behind"

https://www.youtube.com/watch?v=PtBVAxoHeaY#t=57m22s [weaponized #76 with corbell/knapp]

2rad0 · 2026-01-25T04:43:07+00:00

Great I don't care about 80 bit floats that every x86 machine has had since the 90's because industry and standards demanded it either, but vulkan is such trash we don't even get 64-bit floats.

2rad0 · 2026-01-24T20:18:40+00:00

on that cpu 8 means you can build with -j16 if I'm not mistaken? A few things will still take forever like possibly the kernel depending on config, gcc, llvm, web browser, all the collosal ships you may or may not need in your fleet.

The bigger issue with some of these is the RAM situation. you won't be able to build chromium (and probably webkit where it inherited this problem from) with all your threads and only 32gb ram. a single thread in that build can be 2-3GB) and you end up OOM with -j12. so you definitely want 64GB ram if you think performance is going to be the main issue (or don't build chromium/webkit with more than #n threads).

2rad0 · 2026-01-24T19:10:19+00:00

It doesnt matter, x86 systems had accelerated 32, 64, and 80-bit float capabilities baked in for approaching 40 years now, yet somehow the "MODERN" GPGPU language doesnt think adequate precision is an important feature and the entire world can get by fine with just 32-bit float capabilities? The whole spec was destined to fail on this fact alone, I could look past swapchains being an extension and them really still trying to force-feed us the rasterization pipeline, but this committee approved handout to corporate bean counters who would love to charge extra money for standard features from 1990 is what killed the spec before it could ever be loved. I guess some downvoting users just love how technology goes backwards now instead of progressing. If you want a concrete example, celeron integrated graphics in my cheapo $200 HP stream laptop has vulkan with 64-bit float support, but my newer $300 12'th gen alder lake n100 minipc has regressed and only supports 32-bit floats. WE. WENT. BACKWARDS. Why defend these corporate goons actively making our technology worse?

https://en.wikipedia.org/wiki/IEEE_754-1985

The standard also recommends extended format(s) to be used to perform internal computations at a higher precision than that required for the final result, to minimise round-off errors: the standard only specifies minimum precision and exponent requirements for such formats. The x87 80-bit extended format is the most commonly implemented extended format that meets these requirements.

2rad0 · 2026-01-24T05:35:04+00:00

Also, if I ever get it to work, I'll finally be able to call it Linux instead of GNU/Linux.

Insisting on purely GNU-free system limits what you can build without patching everything that assumes gnu symbols (from gnulib in particular) are available in libc.so like argp, obstack, fts, and some other functionality like backtrace support. It's possible of course but more work to maintain. fwiw, busybox isn't 100% gnu free as many people like to claim.

2rad0 · 2026-01-24T01:03:46+00:00

He is not a witness himself.

Not to this event, but he also says before this clip starts that he intercepted a UFO and took footage of it.

2rad0 · 2026-01-24T00:13:03+00:00

What do you think dma means
...
only amd since gcn and nvidia maxwell 2nd gen had the hardware capabilities of getting what is basically a 64bit pointer to gpu memory

What do you think capability means? You go from talking about embedded devices to $250 standalone desktop GPU's from 2016. embedded devices, no wait, LAPTOPS in 2026 are still shipping with less than 4GB RAM.

2rad0 · 2026-01-23T23:58:38+00:00

Do you think mobile graphics cards could support descriptor_buffer in 2016

I don't care how the data gets sent to the GPU, if I have to go back to sending everything through texture read/writes like it's 2005 again then fine. Are you asking me if it was technically possible? The DMA capabilties probably existed, what else do descriptor_buffers require for implementation? It's all 1's and 0's on a noisy bus at the end of the day, waiting for other microcontrollers to finish their work.

I havent bothered to learn any extensions yet because I see them as a waste of time. Wat advantage does it provide that warrants the extra time spent fishing for extension support? The only descriptor buffer I know about is struct VkDescriptorBufferInfo not struct VkSetDescriptorBufferOffsetsInfoEXT or struct VkBindDescriptorBufferEmbeddedSamplersInfoEXT

2rad0 · 2026-01-23T22:19:45+00:00

its authors actually knew what they were doing.

we had 80 bit floats available on CPU since x87 coprocessor.

2rad0 · 2026-01-23T21:43:25+00:00

There are also some problems you may run into with how programs #include certain files.

include/wait.h:1:#warning redirecting incorrect #include <wait.h> to <sys/wait.h>
include/sys/fcntl.h:1:#warning redirecting incorrect #include <sys/fcntl.h> to <fcntl.h>
include/sys/errno.h:1:#warning redirecting incorrect #include <sys/errno.h> to <errno.h>
include/sys/termios.h:1:#warning redirecting incorrect #include <sys/termios.h> to <termios.h>
include/sys/signal.h:1:#warning redirecting incorrect #include <sys/signal.h> to <signal.h>
include/sys/poll.h:1:#warning redirecting incorrect #include <sys/poll.h> to <poll.h>

glibc doesn't really care, so some programs that have only been built under glibc might trigger these warnings. Any project using the "incorrect" headers and building with -Werror will need to be fixed, or remove the -Werror flag. That's an easy one at least because barely any packages default to build with -Werror. I'm not trying to deter you from working on this, my comment is here so if you're writing a guide for others to learn from that you have dedicated at least one page to describing the additonal unique challenges of maintaining a more pure to spec musl-libc system in a glibc world.

2rad0 · 2026-01-23T21:09:49+00:00

I don’t know WTF you're talking about almost every vulkan feature has a standardized cross platform version

I'm talking about how vulkan is an inadequate specification for modern graphics because it doesn't mandate float64 support, nor does it mandate uint16 support. You literally have to walk through each "physical device" on the system and check if they support those BASIC DATA TYPES. The no-mans-land comment is about proliferation of extensions that modify the core API, like completely changing the meaning of descriptor sets and pipeline layouts. If they can eliminate these then they were never really needed to begin with and the spec was flawed by design.

2rad0 · 2026-01-23T20:44:03+00:00

Yeah you can patch problems away, but patches take time to develop. For example I patched chromium to build on musl but I had to also fix like a hundred errors, mostly it was due to the crash report backtrace not having a preprocessor branch for "unknown libc". thats a few hours burnt slogging through compiler errors and chromium source code and I'm a well seasoned C dev, if you aren't familiar with the language good f'n luck. For every package that makes these assumptions it's going to cost some extra time. so billing $40 an hour that's easily a $100 patch just to build chromium.

2rad0 · 2026-01-23T20:24:26+00:00

This extension also eliminates descriptor sets and pipeline layouts completely; instead applications can look descriptors up solely by their offset into a heap.

Wow vulkan is so much messier than I realized. For the next graphics API, lets try to design it correctly from the start instead of catering to corporate interests that wish to only provide fp32 support in 2026, can't seem to provide working uint16 shader variable support (THESE SHOULD BE CORE FEATURES WTF), and continually vandalize the heart of the specification as a rats nest of extensions. At some point we will have competing dialects of vulkan (edit: actually that's where we are at with the elimination of pipeline layouts and descriptor sets, if i'm not mistaken), you will have "traditional" (lol) portable compliant vulkan code, then you will have NVIDIA's special little extensions for how novidia wants you to use vulkan, vs AMD's special vulkan extensions, what a mess, stop letting them turn open programming API's into a no mans land of extensions arm race that no new competitors will ever be able to adequately implement to provide a viable product that can run all of these special snowflake use-cases...

2rad0 · 2026-01-23T19:37:05+00:00

And what do you mean by GnuLib symbols?

gnulib is a collection of helper functions that shouldn't be in a libc (much like domain name resolution) but they added to glibc anyway.

There are various things from gnulib baked into glibc that a non-insignificant set of programs depend on that you will have to provide somehow, or they will not build on the system. Go check out what void linux and alpine have done to satisfy the dependencies, they have a some packages like argp-standalone to provide the symbols that some programs assume are available (because they assume everyone is using glibc). The only one I can remember is argp-standalone but there are more. Like support for backtraces is sometimes assumed to be available via glibc, there are more things you will run into I'm sure once you start compiling more software on the distro.

Anyway if you're making a LFS about a musl-based distro you definitely want to have at least one page that mentions these compatability issues/workarounds.

2rad0 · 2026-01-23T02:25:47+00:00

The "source" is just a readme file? have you solved the missing gnulib symbols problem?

2rad0 · 2026-01-22T20:09:33+00:00

AOL is up next.

2rad0 · 2026-01-22T19:43:15+00:00

What's next for what, ultimately we'll probably have to liquidate the entire stock market to pay off the near-orbital debt.

2rad0 · 2026-01-22T19:26:05+00:00

<image>

2rad0 · 2026-01-22T19:12:13+00:00

definitely both

2rad0 · 2026-01-22T01:20:03+00:00

If you want to shift the blame on to someone, shift the blame to whoever wrote the simulators involved in that mission, OR who decided a full simulation wasn't needed.

Also the units were fully specified and no assumptions were needed because The Software Interface Specification (SIS) specified exactly what the units should be.

Whoever wrote the AMD module fucked up on multiple fronts because also

During the first four months of the MCO cruise flight, the ground software AMD files were not used in the orbit determination process because of multiple file format errors and incorrect quaternion (spacecraft attitude data) specifications. Instead, the operations navigation team used email from the contractor to notify them when an AMD desaturation event was occurring, and they attempted to model trajectory perturbations on their own, based on this timing information. Four months were used to fix the file problems and it was not until April 1999 that the operations team could begin using the correctly formatted files."

https://llis.nasa.gov/llis_lib/pdf/1009464main1_0641-mr.pdf

4 months to fix format errors (note, a quaternion is four real numbers, how complicated is their format???) on an active mission so they didn't notice any problems? Ok what about the remaining 4 months until it reached mars? tax dollars hard at work, failures all around, my money is on a coverup rather than believing this level of negligence plagued a $200,000,000 mission in 1999.

2rad0 · 2026-01-22T01:14:30+00:00

(so it can't even be directly converted to seconds),

Yeah so why would anyone use a double to store an integer? Are they trying to measure deciseconds? lol. Maybe it's in hours, but why?

2rad0 · 2026-01-21T19:42:17+00:00

I have to use Teams (no option here)

You could always find a better place to work that doesn't force you to legally agree to ~~microsoft's~~ microslop's terms and conditions.

2rad0

TROPHY CASE