4 ms·
Missed the part? > Most likely we will still need some kind of formalisation tools to tame natural language uncertainties, however most certainly they won't be
by pjmlp 2y ago
Missed the part?
> Most likely we will still need some kind of formalisation tools to tame natural language uncertainties, however most certainly they won't be Python/Rust like
- Wowfunhappy 2y agoNo, I didn't miss it. I think the fact that LLMs are non deterministic means we'll need a lot more than "some kind of formalization tools", we'll need real programming languages for some applications!
- pjmlp 2y agoHow deterministic are C compilers at -O3, while compiling exactly the same code across various kinds of vector instructions, and GPUs? We are already on the baby steps down that path, https://code.visualstudio.com/docs/copilot/copilot-customization https://code.visualstudio.com/docs/copilot/copilot-customiza...
- spookie 2y agoTake a look at the following: https://reproduce.debian.net/ https://reproduce.debian.net/ Granted, lot's of different compilers and arguments depending on packages. But you need to match this reproducibility in a fancy pants 7GL
- pjmlp 2y agoAnd still its behaviour isn't guaranteeded if the hardware isn't exactly the same as where the binaries were produced. That is why on high integrity computing all layers are certified, and any tiny change requires a full stack re-certification.
- saagarjha 2y agoThere is a world of difference between "my code is generated by an LLM where a tiny change in the prompt might produce an entirely different program" and "this CPU doesn't have AVX2".
- almostgotcaught 2y agoYou moved the goal posts and declared victory - that's not what deterministic means. It means same source, same flags, same output. Under that definition, the actual definition, they're 99.9% deterministic (we strive for 100% but bugs do happen).
- pjmlp 2y agoNope the goal stayed at the same position, people argue for deterministic results while using tools that by definition aren't deterministic unless a big chunck of work is done ensuring that it is indeed. "It means same source, same flags, same output", it suffices to change the CPU and the Assembly behaviour might not be the same.
- almostgotcaught 2y agoDo you like have any idea what you're talking about? Or are you just making it up for internet points? The target is part of the input. Lemme ELI5 https://github.com/llvm/llvm-project/tree/main/llvm/test/CodeGen https://github.com/llvm/llvm-project/tree/main/llvm/test/Cod... You see how this folder has folders for each target? Then within each target folder there are tests (thousands of tests)? Each of those tests is verified deterministically on each commit. Edit: there's an even more practical way to understand how you're wrong: if what you were saying were true, ccache wouldn't work.
- sitkack 2y agoYou keep being you, but you also have to admit, not only do you move goal posts, but most of arguments are on dollies, performing elaborate choreographies that would make Merce Cunningham blush.
- fulafel 2y agopjmlp did originally say "compiling exactly the same code across various kinds of vector instructions, and GPUs".
- ModernMech 2y ago