3 ms·
Hot take, this is a transition step, like the -S switch back when Assembly developers didn't believe compilers could output code as good as themselves. Eventua
by pjmlp 2y ago
Hot take, this is a transition step, like the -S switch back when Assembly developers didn't believe compilers could output code as good as themselves.
Eventually a few decades later, optimising backends made hand written Assembly a niche use case.
Eventually AI based programming tools will be able to generate executables. And like it happened with -S we might require the generation into a classical programming language to validate what the AI compiler backend is doing, until it gets good enough and only those arguing on AI Compiler Explorer will care.
- secondcoming 2y agoIt's probably pointless writing run of the mill assembly these days, but SIMD has seen a resurgence in low-level coding, at least until compilers get better at generating it. I don't think I'd fully trust LLM generated SIMD code as if it was flawed it'd be a nightmare to debug.
- pjmlp 2y agoWell, that won't stop folks trying though. "Nova: Generative Language Models for Assembly Code with Hierarchical Attention and Contrastive Learning" https://arxiv.org/html/2311.13721v3 https://arxiv.org/html/2311.13721v3
- imtringued 2y agoThis won't be a thing and for very obvious reasons. Programming languages solve the specification problem, (which happens to be equivalent to "The Control Problem"). If you want the computer to behave in a certain way, you will have to provide a complete specification of the behavior. The more loose and informal that specification is, the more blanks have to be filled in, the more you are letting the AI make decisions for you. You tell your robotic chef to make a pizza, and he does, but it turns out it decided to make a vegan pizza. You yell at the robot for making a mistake and it sure gets that you don't want a vegan pizza, so it decides to add canned tuna. Except, turns out you don't like tuna either. You yell at the robot again and again until it gets it. Every single time you're telling the AI that it made a mistake, you're actually providing a negative specification of what not to do. In the extreme case you will have to give the AI an exhaustive list of your preferences and dislikes, in other words, a complete specification. By directly producing executables, you have reduced the number of knobs and levers that can be used to steer the AI and made it that much harder to provide a specification of what the application is supposed to do. In other words, you're assuming that the model in itself is already a complete specification and your prompt is just retrieving the already existing specification.
- pjmlp 2y agoThat was the argument from many Assembly developers against FORTRAN compilers, if you dive into literature of the time. Also this is already happening in low code SaaS products where integrations have now AI on their workflows. For example, https://www.sitecore.com/products/xm-cloud/ai-workflow https://www.sitecore.com/products/xm-cloud/ai-workflow Which in a way are like high level interpreters, and eventually we will have compilers as well. Not saying it happen tomorrow, but it will come.
- antonvs 2y ago> Programming languages solve the specification problem, (which happens to be equivalent to "The Control Problem"). Not equivalent, for several reasons. An obvious one is simply that even providing a perfect specification in fact does nothing to solve the control problem, because you still have to enforce following of the specification. It's similar to the human version of the control problem: we can write comprehensive and copious laws, but that doesn't automatically prevent humans from breaking them. Besides that, the control problem is inherently subjective. The difficulty of breaking it down into an exhaustive list of deterministic rules is a big part of the problem, which programming languages do nothing to solve.