Subject: bug#77840: [bug-diffutils] bug#77840: Testing diffutils 3.12 on PPC Mac OS X 10.4.11, Tiger, produces so many failures

From: Peter Dyballa <[email-masked]>
Date: Tue, 24 Jun 2025 17:24:20 +0200

> Am 24.06.2025 um 13:09 schrieb Peter Dyballa <[email-masked]>:
> 
> It presumingly happens in shift_boundaries().

No, it does not happen there, because filevec|cmp|curr is not changed. The function reads the component changed but does not write back. It just wastes time? I cannot see that the function's results are saved anywhere and are used somewhere else…

The following function called from diff_2_files() is already build_script() from type declaration of struct change *script. Before, I found that build_script() already uses faulty data, so it's compareseq (), the function that gets called before build_script() and shift_boundaries(), that creates the faulty data values?

--

Greetings

  Pete

A monsoon is a French gentleman.