olcott <NoOne@NoWhere.com> writes:
On 5/20/2022 11:26 AM, Ben wrote:
olcott <NoOne@NoWhere.com> writes:
On 5/20/2022 10:12 AM, Ben wrote:I really don't care. The trace of a nested emulation would not look
olcott <NoOne@NoWhere.com> writes:
On 5/20/2022 6:25 AM, Ben wrote:
olcott <NoOne@NoWhere.com> writes:
On 5/19/2022 7:53 PM, Ben wrote:(Your correction added)
olcott <NoOne@NoWhere.com> writes:
ONE CAN VERIFY THAT THE EXECUTION TRACE IS CORRECT ON THE BASIS THAT >>>>>>>>>> THE EXECUTION TRACE OF THE INPUT TO H(P,P) CORRESPONDS TO
THE BEHAVIOR SPECIFIED BY THE X86 SOURCE-CODE OF P
WHERE H(P,P) CORRECTLY EMULATES ITS INPUT
THAT CALLS H(P,P) THAT CORRECTLY EMULATES ITS INPUT
Rather than shouting, you could either publish an honest, un-edited >>>>>>>>> execution trace,
If you can't understand that a single page already proves that >>>>>>>> H(p,P)==0 is correct it is certainly the case that providing 237-fold >>>>>>>> more details [would not help].
Your traces are edited. No one will believe them until you post the >>>>>>> real trace, and even then you will have some work to do to convince >>>>>>> people you are being honest about the output.
I can simply upgrade to smarter people that don't lie.
I don't lie. Your trace does not show what you claim H is doing.
That is either a lie or you are very stupid and I do not believe that
you are very stupid.
like your trace.
This <is> the trace of the nested emulation of the input to H(P,P)
So you say. But there are no signs of anything but an edited sequence
of function calls. No emulation code appears at all. You may have
removed the evidence that you are right, but that would an absurd thing
to do.
You will be exposed as a liar when you try to show any error in the
execution trace of the nested simulation of the input to H(P,P).
Post H and I'll gladly explain. We know that H is not a halt decider,
but we don't know exactly what silly thing it really is deciding because
you post only edited execution traces.
On 5/20/2022 11:41 AM, Ben wrote:
olcott <NoOne@NoWhere.com> writes:
On 5/20/2022 11:26 AM, Ben wrote:
olcott <NoOne@NoWhere.com> writes:
On 5/20/2022 10:12 AM, Ben wrote:I really don't care. The trace of a nested emulation would not look
olcott <NoOne@NoWhere.com> writes:
On 5/20/2022 6:25 AM, Ben wrote:
olcott <NoOne@NoWhere.com> writes:
On 5/19/2022 7:53 PM, Ben wrote:(Your correction added)
olcott <NoOne@NoWhere.com> writes:
ONE CAN VERIFY THAT THE EXECUTION TRACE IS CORRECT ON THE >>>>>>>>>>> BASIS THAT
THE EXECUTION TRACE OF THE INPUT TO H(P,P) CORRESPONDS TO >>>>>>>>>>> THE BEHAVIOR SPECIFIED BY THE X86 SOURCE-CODE OF P
WHERE H(P,P) CORRECTLY EMULATES ITS INPUT
THAT CALLS H(P,P) THAT CORRECTLY EMULATES ITS INPUT
Rather than shouting, you could either publish an honest,
un-edited
execution trace,
If you can't understand that a single page already proves that >>>>>>>>> H(p,P)==0 is correct it is certainly the case that providing >>>>>>>>> 237-fold
more details [would not help].
Your traces are edited. No one will believe them until you post >>>>>>>> the
real trace, and even then you will have some work to do to convince >>>>>>>> people you are being honest about the output.
I can simply upgrade to smarter people that don't lie.
I don't lie. Your trace does not show what you claim H is doing.
That is either a lie or you are very stupid and I do not believe that >>>>> you are very stupid.
like your trace.
This <is> the trace of the nested emulation of the input to H(P,P)
So you say. But there are no signs of anything but an edited sequence
of function calls. No emulation code appears at all. You may have
removed the evidence that you are right, but that would an absurd thing
to do.
NONE-THE-LESS WHEN WE REVERSE ENGINEER WHAT THE CORRECT NESTED
SIMULATION OF THE INPUT TO H(P,P) WOULD BE IT EXACTLY MATCHES THE TRACE
THAT IS PROVIDED THUS CONCLUSIVELY PROVING THAT THE TRACE PROVIDED IS CORRECT.
You will be exposed as a liar when you try to show any error in the
execution trace of the nested simulation of the input to H(P,P).
Post H and I'll gladly explain. We know that H is not a halt decider,
but we don't know exactly what silly thing it really is deciding because
you post only edited execution traces.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 427 |
Nodes: | 16 (3 / 13) |
Uptime: | 34:13:49 |
Calls: | 9,029 |
Calls today: | 12 |
Files: | 13,384 |
Messages: | 6,008,751 |