Re: No decider is ever accountable for the behavior of the computation that itself is contained within DETAILS

Liste des GroupesRevenir à theory 
Sujet : Re: No decider is ever accountable for the behavior of the computation that itself is contained within DETAILS
De : polcott333 (at) *nospam* gmail.com (olcott)
Groupes : comp.theory
Date : 27. Jul 2024, 14:41:54
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <v82tf4$3dftr$1@dont-email.me>
References : 1 2
User-Agent : Mozilla Thunderbird
On 7/27/2024 3:59 AM, Mad Hamish wrote:
On Fri, 26 Jul 2024 11:28:43 -0500, olcott <polcott333@gmail.com>
wrote:
 
No decider is ever accountable for the behavior of the
computation that itself is contained within.>
It is only accountable for computing the mapping from the
input finite string to the actual behavior that this finite
string specifies.
>
 You might want to actually work on definitions rather than shouting
out word salad
Which definitions do you need?
Computing the mapping from a finite string of x86 machine
language to its actual behavior is the most difficult one.
Because HHH is an x86 emulator it merely emulates its input
including emulating itself emulating its input. That is how
the mapping is computed.
Knowing the semantics of the x86 language is also required, the
best that I can do here is annotate the code. I provide the C
source code to make that easier.
typedef void (*ptr)();
int HHH(ptr P);
void DDD()
{
   HHH(DDD);
}
int main()
{
   DDD();
}
*H is a termination analyzer based on an x86 emulator*
The only two things that need to be known about HHH is that:
(a) It emulates its input in DebugStep() mode
(b) It stops emulating its input when it seen a
non-terminating behavior pattern.
*Here is the C source code of DDD, HHH and supporting functions*
https://github.com/plolcott/x86utm/blob/master/Halt7.c
*This function switches process context from HHH to DDD*
*to emulate one x86 machine language instruction of DDD*
*then switches back to HHH*
u32  DebugStep(Registers* master_state,
                Registers* slave_state,
                Decoded_Line_Of_Code* decoded) { return 0; }
typedef struct Decoded
{
   u32 Address;
   u32 ESP;          // Current value of ESP
   u32 TOS;          // Current value of Top of Stack
   u32 NumBytes;
   u32 Simplified_Opcode;
   u32 Decode_Target;
} Decoded_Line_Of_Code;
Immediately before an instruction is emulated HHH
searches a scratch build std::vector<Decoded> execution_trace;
Looking for a non-halting behavior pattern.
An x86utm operating system function provides PushBack()
void PushBack(u32 stdvector, u32 data_ptr, u32 size_in_bytes) {}
An x86utm operating system function allocated memory
u32* Allocate(u32 size) { return 0; }
--
Copyright 2024 Olcott "Talent hits a target no one else can hit; Genius
hits a target no one else can see." Arthur Schopenhauer

Date Sujet#  Auteur
26 Jul 24 * No decider is ever accountable for the behavior of the computation that itself is contained within45olcott
26 Jul 24 +* Re: No decider is ever accountable for the behavior of the computation that itself is contained within6olcott
26 Jul 24 i+* Re: No decider is ever accountable for the behavior of the computation that itself is contained within3olcott
27 Jul 24 ii+- Re: No decider is ever accountable for the behavior of the computation that itself is contained within (unless that is its input)1Richard Damon
27 Jul 24 ii`- Re: No decider is ever accountable for the behavior of the computation that itself is contained within1Fred. Zwarts
27 Jul 24 i+- Re: No decider is ever accountable for the behavior of the computation that itself is contained within (unless that is its input)1Richard Damon
27 Jul 24 i`- Re: No decider is ever accountable for the behavior of the computation that itself is contained within1Fred. Zwarts
27 Jul 24 +- Re: No decider is ever accountable for the behavior of the computation that itself is contained within (Unless that is its input)1Richard Damon
27 Jul 24 +* Re: No decider is ever accountable for the behavior of the computation that itself is contained within32Mikko
27 Jul 24 i`* Re: No decider is ever accountable for the behavior of the computation that itself is contained within31olcott
27 Jul 24 i +- Re: No decider is ever accountable for the behavior of the computation that itself is contained within1Fred. Zwarts
28 Jul 24 i +- Re: No decider is ever accountable for the behavior of the computation that itself is contained within, unless that is what the input descriibes1Richard Damon
28 Jul 24 i `* Re: No decider is ever accountable for the behavior of the computation that itself is contained within28Mikko
29 Jul 24 i  `* Re: No decider is ever accountable for the behavior of the computation that itself is contained within27olcott
29 Jul 24 i   +* Re: No decider is accountable for the computation that itself is contained within19joes
29 Jul 24 i   i`* Re: No decider is accountable for the computation that itself is contained within18olcott
30 Jul 24 i   i `* Re: No decider is accountable for the computation that itself is contained within17joes
30 Jul 24 i   i  `* Re: No decider is accountable for the computation that itself is contained within16olcott
30 Jul 24 i   i   +* Re: No decider is accountable for the computation that itself is contained within4Fred. Zwarts
30 Jul 24 i   i   i`* Re: No decider is accountable for the computation that itself is contained within3olcott
31 Jul 24 i   i   i +- Re: No decider is accountable for the computation that itself is contained within, unless that is its input1Richard Damon
31 Jul 24 i   i   i `- Re: No decider is accountable for the computation that itself is contained within1Fred. Zwarts
30 Jul 24 i   i   +* Re: No decider is accountable for the computation that itself is contained within10joes
30 Jul 24 i   i   i`* Re: No decider is accountable for the computation that itself is contained within9olcott
30 Jul 24 i   i   i +* Re: No decider is accountable for the computation that itself is contained within7joes
30 Jul 24 i   i   i i`* Re: No decider is accountable for the computation that itself is contained within6olcott
31 Jul 24 i   i   i i +* Re: No decider is accountable for the computation that itself is contained within4Mike Terry
31 Jul 24 i   i   i i i`* Re: No decider is accountable for the computation that itself is contained within3olcott
31 Jul 24 i   i   i i i +- Re: No decider is accountable for the computation that itself is contained within, unless that is its input1Richard Damon
31 Jul 24 i   i   i i i `- Re: No decider is accountable for the computation that itself is contained within1Fred. Zwarts
31 Jul 24 i   i   i i `- Re: No decider is accountable for the computation that itself is contained within1Fred. Zwarts
31 Jul 24 i   i   i `- Re: No decider is accountable for the computation that itself is contained within, unless that is its input1Richard Damon
31 Jul 24 i   i   `- Re: No decider is accountable for the computation that itself is contained within, unless that is its input1Richard Damon
30 Jul 24 i   +- Re: No decider is ever accountable for the behavior of the computation that itself is contained within UNLESS that is what the input actually describes1Richard Damon
30 Jul 24 i   `* Re: No decider is ever accountable for the behavior of the computation that itself is contained within6Mikko
31 Jul 24 i    `* Re: No decider is ever accountable for the behavior of the computation that itself is contained within5olcott
1 Aug 24 i     `* Re: No decider is ever accountable for the behavior of the computation that itself is contained within4Mikko
1 Aug 24 i      `* Re: No decider is ever accountable for the behavior of the computation that itself is contained within3olcott
1 Aug 24 i       +- Re: No decider is ever accountable for the behavior of the computation that itself is contained within1joes
2 Aug 24 i       `- Re: No decider is ever accountable for the behavior of the computation that itself is contained within1Mikko
27 Jul 24 +- Re: No decider is ever accountable for the behavior of the computation that itself is contained within1Fred. Zwarts
27 Jul 24 `* Re: No decider is ever accountable for the behavior of the computation that itself is contained within4Mad Hamish
27 Jul 24  +* Re: No decider is ever accountable for the behavior of the computation that itself is contained within DETAILS2olcott
28 Jul 24  i`- Re: No decider is ever accountable for the behavior of the computation that itself is contained within DETAILS unless that is what the input is representing.1Richard Damon
28 Jul 24  `- Re: No decider is ever accountable for the behavior of the computation that itself is contained within1Mikko

Haut de la page

Les messages affichés proviennent d'usenet.

NewsPortal