Re: Even Google AI Overview understands me now --- different execution traces have different behavior !!!

On 10/6/24 3:00 PM, olcott wrote:

On 10/6/2024 1:52 PM, Richard Damon wrote:

On 10/6/24 2:32 PM, olcott wrote:

On 10/6/2024 1:13 PM, Richard Damon wrote:

On 10/6/24 2:03 PM, olcott wrote:

On 10/6/2024 12:29 PM, Richard Damon wrote:

On 10/6/24 1:07 PM, olcott wrote:

On 10/6/2024 11:59 AM, Richard Damon wrote:

On 10/6/24 8:39 AM, olcott wrote:

>
DDD emulated by each corresponding HHH that can possibly
exist never returns. Each of these HHH emulators that does
return 0 correctly reports the above non-halting behavior.
>
>

>
>
No, the DDD return (if the HHH(DDD) gives an answer), just after the HHH that emulated them gave up.
>

>
DDD emulated by each corresponding HHH that can possibly
exist never returns.
>
DDD emulated by each corresponding HHH
DDD emulated by each corresponding HHH
DDD emulated by each corresponding HHH
DDD emulated by each corresponding HHH

>
Which, as you have been told but seems to be above your head means that the execution of DDD,

>
gets to ignore the fact that DDD was defined to
have a pathological relationship with HHH that
HHH cannot ignore.
>

>
No, that isn't ignoring it, but taking into account that since HHH is defined to be a specific program, it has specific behavior.
>

>
The behavior of the executed DDD after the emulated
DDD has already been aborted is different than the
behavior of the emulated DDD that must be aborted.

>
Nope, it is the exact same code on the exact same data, and thus does the exact same behavior.
>

 The execution trace proves that the executed DDD has
different behavior that need not be aborted because
emulated DDD must be an is aborted.

Really? What instruction actually emulated had a different result than when it was executed.
All you do is look at a DIFFERENT INPUT which is just a lie, since that isn't the DDD that HHH was given (since the PROGRAM DDD includes the all the exact code of the HHH that it calls, thus you can't change it to hypothosze a diffferent non-aborting HHH)

 No one can be stupid enough to think that
NEED NOT BE ABORTED is exactly the same as NEED NOT BE ABORTED
 

No, but the fact that it DOES abort it simulation means its simulation doesn't show the actual behavior of the input, and means that an actual correct simulation will halt.
In other words, you are just proving that
PPPP   EEEEE  TTTTT  EEEEE  RRRR
P   P  E        T    E      R   R
P   P  E        T    E      R   R
PPPP   EEEEE    T    EEEEE  RRRR
P      E        T    E      R R
P      E        T    E      R  R
P      EEEEE    T    EEEEE  R   R
  OOO   L       CCC    OOO   TTTTT  TTTTT
O   O  L      C   C  O   O    T      T
O   O  L      C      O   O    T      T
O   O  L      C      O   O    T      T
O   O  L      C      O   O    T      T
O   O  L      C   C  O   O    T      T
  OOO   LLLLL   CCC    OOO     T      T
L     IIIII  EEEEE   SSS
L       I    E      S   S
L       I    E      S
L       I    EEEEE   SSS
L       I    E          S
L       I    E      S   S
LLLLL IIIII  EEEEE   SSS
AND THINKS THAT IS JUST OK.