Multiple independently created compilers can directly translate source code to unoptimized machine code that works in a completely straightforward fashion based on the definition of the language. There’s a great deal of complexity involved in creating more optimized output, but the goal is to have functionally equivalent programs.
There’s no way to map DALLE prompts into any kind of obvious picture from the input. Even DALLE itself can produce a wide range of outputs from a single input.
There is, the input is the description of the image so produced plus the hidden elements and parameters (randomness, etc) that users often don't see - with these there is a deterministic input to output relationship. The fitness of the model is in how closely the output matches what we expect to see from them given the inputs we give. That's the point of them. Models are compilers. The distinction is really only in the complexity and ambiguity of the language specifications they implement - not in any fundamental aspect of their function. There isn't a single person alive who understands how a non-trivial compiler works in its entirety, just as nobody really knows how LLMs work yet. That's not the point.
That’s not “independently created” you’re suggesting reimplementing the output of a process not from first principles but from the output of the process. I can make a compiler in a programming language without it being a derivative work of any other compiler.
Further, people have programmed in languages before any compilers where created which worked after the compilers where created.
The CPU is a compiler for programs written in the machine instruction set architecture the CPU claims to implement which happens to output real world effects just as a compiler outputs program code. So, no, you can't.
Words have meanings, and the instruction pipeline consists of electrical signals - and those early CPUs were almost all microcoded or had multiphase clocks or some other implementation abstraction which they did not expose to their architectural state... so yes, they were in a very real sense compilers.
Simply because I didn't state "for all and every" doesn't invalidate my point, nor does it support yours as true - further, "heavily favored" suffers from the same problem. The point is, there's a system which takes as input formatted in a specification (a program) and some transformed output (a set of actions to be taken or another program input for another compiler). So, there you go. If a hot dog on a bun could be considered a sandwich, then a CPU could be considered to be a compiler. shrug disagree all you like.
If you say X is Y, but it’s not true for all X then the statement is false. Ie: “All integers are even.” is false.
As to your point that’s not what CPU’s do though, they have both a set of instructions and a set of IO with the outside world. A compiler always results in the same output from a given set of instructions, but with CPU’s you can run the same code and get wildly different output due to that IO.
The only way you can call a CPU a compiler is as a subset of its capabilities. If they they have internal microcodes where a given instruction gets translated into a different internal representation, but that’s not the end it also executes those microcodes.
There’s no way to map DALLE prompts into any kind of obvious picture from the input. Even DALLE itself can produce a wide range of outputs from a single input.