Re: FYI: WITH_REPRODUCIBLE_BUILD= problem for some files? [aarch64 test did not reproduce the issue]

On 2021-May-4, at 20:26, Mark Millard <marklmi at yahoo.com> wrote:

> On 2021-May-4, at 13:38, Mark Millard <marklmi at yahoo.com> wrote:
> 
>> [The first buidlworld is still in process. So while waiting . . .]
>> 
>> On 2021-May-4, at 10:31, Mark Millard <marklmi at yahoo.com> wrote:
>> 
>>> I probably know why the huge count of differences this time
>>> unlike the original report . . .
>>> 
>>> Previously I built based on a checked-in branch as part of
>>> my experimenting. This time it was in a -dirty form (not
>>> checked in), again as part of my experimental exploration.
>>> 
>>> WITH_REPRODUCIBLE_BUILD= makes a distinction between these
>>> if I remember right: (partially?) disabling itself for
>>> -dirty style.
>>> 
>>> To reproduce the original style of test I need to create
>>> a branch with my few patches checked in and do the
>>> buildworlds from that branch.
>>> 
>>> This will, of course, take a while.
>>> 
>>> Sorry for the noise.
>>> 
>> 
>> I've confirmed some of the details of the large number of
>> files with difference while waiting for the 1st buildworld :
>> 
>> The 4 bytes at the end of the .gnu_debuglink section
>> that are ending up different are the checksum for the
>> .debug file. The .debug files have differences such as:
>> 
>> │ -    <1a>   DW_AT_comp_dir    : (indirect string) /usr/obj/BUILDs/13_0R-CA72-nodbg-clang-alt/usr/13_0R-src/arm64.aarch64/lib/csu/aarch64
>> │ +    <1a>   DW_AT_comp_dir    : (indirect string) /usr/obj/BUILDs/13_0R-CA72-nodbg-clang/usr/13_0R-src/arm64.aarch64/lib/csu/aarch64
>> 
>> So I need to build, snapshot (in case need
>> to reference), install, clean-out, build,
>> install elsewhere, compare. (Or analogous
>> that uses the same build base-path for both
>> installs despite separate buildworld's.)
>> This is separate from any potential -dirty
>> vs. checked-in handling variation by
>> WITH_REPRODUCIBLE_BUILD= .
>> 
>> My process that produced the original armv7
>> report happened to do that before I accidentally
>> discovered the presence of the few files with
>> differences. My new experiments were different
>> and I'd not though of needing to vary the
>> procedure to get you the right evidence.
>> 
> 
> The two aarch64 test installs did not show any
> differences in a "diff -rq" . Ignoring *.meta
> files generated during the builds, the build
> directory tree snapshots showed just the
> differences:
> 
> # diff -rq /usr/obj/BUILDs/13_0R-CA72-nodbg-clang-alt/.zfs/snapshot/commited-style-0/usr /usr/obj/BUILDs/13_0R-CA72-nodbg-clang-alt/.zfs/snapshot/commited-style-1/usr | grep -v '\.meta' | more
> Files /usr/obj/BUILDs/13_0R-CA72-nodbg-clang-alt/.zfs/snapshot/commited-style-0/usr/13_0R-src/arm64.aarch64/stand/ficl/softcore.c and /usr/obj/BUILDs/13_0R-CA72-nodbg-clang-alt/.zfs/snapshot/commited-style-1/usr/13_0R-src/arm64.aarch64/stand/ficl/softcore.c differ
> Files /usr/obj/BUILDs/13_0R-CA72-nodbg-clang-alt/.zfs/snapshot/commited-style-0/usr/13_0R-src/arm64.aarch64/toolchain-metadata.mk and /usr/obj/BUILDs/13_0R-CA72-nodbg-clang-alt/.zfs/snapshot/commited-style-1/usr/13_0R-src/arm64.aarch64/toolchain-metadata.mk differ
> 
> # diff -u /usr/obj/BUILDs/13_0R-CA72-nodbg-clang-alt/.zfs/snapshot/commited-style-0/usr/13_0R-src/arm64.aarch64/stand/ficl/softcore.c /usr/obj/BUILDs/13_0R-CA72-nodbg-clang-alt/.zfs/snapshot/commited-style-1/usr/13_0R-src/arm64.aarch64/stand/ficl/softcore.c
> --- /usr/obj/BUILDs/13_0R-CA72-nodbg-clang-alt/.zfs/snapshot/commited-style-0/usr/13_0R-src/arm64.aarch64/stand/ficl/softcore.c 2021-05-04 13:45:14.463351000 -0700
> +++ /usr/obj/BUILDs/13_0R-CA72-nodbg-clang-alt/.zfs/snapshot/commited-style-1/usr/13_0R-src/arm64.aarch64/stand/ficl/softcore.c 2021-05-04 19:04:32.338203000 -0700
> _at__at_ -4,7 +4,7 _at__at_
> ** Words from CORE set written in FICL
> ** Author: John Sadler (john_sadler_at_alum.mit.edu)
> ** Created: 27 December 1997
> -** Last update: Tue May  4 13:45:14 PDT 2021
> +** Last update: Tue May  4 19:04:32 PDT 2021
> *******************************************************************/
> /*
> ** DO NOT EDIT THIS FILE -- it is generated by softwords/softcore.awk
> 
> # diff -u /usr/obj/BUILDs/13_0R-CA72-nodbg-clang-alt/.zfs/snapshot/commited-style-0/usr/13_0R-src/arm64.aarch64/toolchain-metadata.mk /usr/obj/BUILDs/13_0R-CA72-nodbg-clang-alt/.zfs/snapshot/commited-style-1/usr/13_0R-src/arm64.aarch64/toolchain-metadata.mk
> --- /usr/obj/BUILDs/13_0R-CA72-nodbg-clang-alt/.zfs/snapshot/commited-style-0/usr/13_0R-src/arm64.aarch64/toolchain-metadata.mk 2021-05-04 10:55:26.030179000 -0700
> +++ /usr/obj/BUILDs/13_0R-CA72-nodbg-clang-alt/.zfs/snapshot/commited-style-1/usr/13_0R-src/arm64.aarch64/toolchain-metadata.mk 2021-05-04 16:14:24.513346000 -0700
> _at__at_ -1,4 +1,4 _at__at_
> -.info Using cached toolchain metadata from build at CA72_4c8G_ZFS on Tue May  4 10:55:26 PDT 2021
> +.info Using cached toolchain metadata from build at CA72_4c8G_ZFS on Tue May  4 16:14:24 PDT 2021
> _LOADED_TOOLCHAIN_METADATA=t
> COMPILER_VERSION=110001
> X_COMPILER_VERSION=110001
> 
> 
> 
> I may run a 'target cortex-a7 (so: armv7) from aarch64' test
> next. That was the context for the original discovery and
> report.
> 
> 

The armv7 builds and installs get the same sort of diff
results as the aarch64 ones.

So it does not look like I can readily reproduce the
problem files that had differences.

Given the time it takes to run the experiments, I would
not expect to reproduce the problem on any given
timescale. I'll stop the reporting as I go along in
my activities --unless I end up with a repetition
of the problem.

===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)