And your loose definition isn't doing a lot of help either, beyond perhaps noting: that Google search bar _is_ similarly "intelligent" to an LLM? Which says what, a lot about search? A lot about modern LLMs?
2,300 karma · joined December 14, 2020
And your loose definition isn't doing a lot of help either, beyond perhaps noting: that Google search bar _is_ similarly "intelligent" to an LLM? Which says what, a lot about search? A lot about modern LLMs?
These aren't interesting questions. As much as any definition is in use here, we're not going to get much value talking about "intelligence" this way.
I also don't ascribe intelligence to a pocket calculator.
Obligatory "yes, I know that's not what an LLM is", purely pointing out the metric.
So does the Google search bar, but I don't ascribe intelligence to it.
amd64: https://devblogs.microsoft.com/oldnewthing/20260319-00/?p=11...
arm64: https://devblogs.microsoft.com/oldnewthing/20260320-00/?p=11...
> At some point, the decision was made to just give up and declare it an operating system DLL, to be used only by operating system components.
https://devblogs.microsoft.com/oldnewthing/20140411-00/?p=12...
The Windows ecosystem, that manages to deliver built binaries easily & widely, regardless of whether the author has a 1 year old OS or a 15 year old OS, suggests that it's not as big a problem as you believe.
MS haven't made this work arbitrarily far back, I believe they deprecated targeting Windows XP in one of the more recent toolchains, but that was purely a "not worth supporting" situation.
EDIT: mixed up talking about older & newer
Windows explicitly does not want you to link the system libc. You are expected to bring your own, and doing so means your process has multiple libc's loaded into its address space.
And if you choose to build a binary that doesn't need a libc, you won't be bringing one.
One of the ways Windows manages to support multiple libc's is by being careful not to mix allocators; if a system API you call allocates on your behalf, your libc can't free it, the system API will offer a function to free it.
Windows loader is certainly available to user programs though; LoadLibrary has been around longer than many developers.
It's been less than 24 hours since an OOM killer was identified as responsible for a bug I was experiencing.
Inter-compiler interop is also in play when the two compilers are the same one at different versions, or even potentially flags.
What should it choose then? I have a Zen 3 processor, and benchmarking some simd I did recently says 32 byte or 64 byte chunks was fastest. But I'm sure I'd get a different result on a different Zen, and different again on Intel's.
How would the library decide what SIMD width I should use?