Liste des Groupes | Revenir à theory |
On 4/22/2025 7:57 AM, joes wrote:The processor gets the exact same information, and HHH has access to anAm Tue, 15 Apr 2025 15:44:06 -0500 schrieb olcott:On 4/15/2025 2:03 PM, dbush wrote:On 4/15/2025 2:50 PM, olcott wrote:On 4/15/2025 11:05 AM, dbush wrote:On 4/15/2025 11:29 AM, olcott wrote:What else is it missing that the processor uses to execute it?You continue to stupidly insist that int sum(int x, int y) {return x +That doesn't refute anything I said.*corresponding output to the input**corresponding output to the input*So the algorithm HHH that you've implemented computes *some*
Not freaking allowed to look at any damn thing else besides the
freaking input. Must compute whatever mapping ACTUALLY EXISTS FROM
THIS INPUT.
computable function, but it does not compute the halting function
as it is not computable.
y; }
returns 7 for sum(3,2) because you incorrectly understand how these
things fundamentally work.
It is stupidly wrong to expect HHH(DD) report on the direct execution
of DD when you are not telling it one damn thing about this direct
execution.
libx86emu <is> a correct x86 processor and does emulate its inputsNo, it aborts instead of halting.
correctly.
The key thing here is that everyone has consistently flat out lied aboutDon't project. If HHH does not map DD to its direct execution, it is
the mapping from the above machine code to the behavior of DD emulated
by HHH including HHH emulating itself emulating DD. They do this as a
trollish head game.
Everyone here stupidly assumes that the output must be derived fromNo, the program DD halts when directly executed, which is what we are
something THAT THE INPUT DOES NOT SAY.
HHH emulates DD including emulating itself emulating DD according theDespite multiple requests, you have never pointed to a disagreement with
the semantics of the x86 language. Disagreeing with the semantics of the
x86 language is as stupid as disagreeing with arithmetic.
Les messages affichés proviennent d'usenet.