That's essentially the point. There is a non-zero risk that any given AI company ends up like those examples. That's why they are racing to IPO, raise more, get ahead of each other, and reach escape velocity of that risk.
Even the smallest margin or error in the demand forecast will put them at a huge loss, I can't imagine sleeping well at night if I was on that management team.
Well, you don't. That's why 1.58-bit (ternary) quants are often used. But if that's what they're going for, no need to dress it up in a floating-point facade.
Indeed there are some bugs/"non standard behavior" regarding very small or very big floating point values. All of those where proven harmless for LLM inference. Thanks for pointing out the bug. If you caught something outside of that, please point that out so I can fix it ;)
Yup, the tests already compare to a CPU hugginsface implementation, but I'm working on making running and verifying the results of those tests easier and more available. Also, working on fixing those bugs and make the code more reliable now that the underling hardware has been saturated (memory bound)
reply