Re: toolchain/57466

[Jan-Benedict Glaw <jbglaw%lug-owl.de@localhost>]

The following reply was made to PR toolchain/57466; it has been noted by GNATS.

From: Jan-Benedict Glaw <jbglaw%lug-owl.de@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: toolchain/57466
Date: Fri, 16 Jun 2023 00:16:46 +0200

 --hi5gnoo3wgobr4uk
 Content-Type: text/plain; charset=utf-8
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 
 Hi!
 
 Just to keep my observations on record:
 
   * Supplying -O <dir> to build.sh leads to differences all over,
     which mostly can be dealt with by using the patch I suggested.
 
   * Supplying -M <dir> instead works. Also works with the suggested
     patch. Then, the below mentioned differences for the "comp" set
     will vanish.
 
   * Without -O (and possibly using -M) things mostly work out quite
     well. I'm using vax and amd64 builds for my testing, they both
     have similar remaining differences where the source path shows up
     in the binaries (which isn't caught by the repro build script as
     it seems to start off with the same source dir for its two builds.)
 
       * The "tests" set has differences in the two ubsan tests. GCC's
         ubsan code seems to add the source's filename, but that's not
         caught by either the remapping regexps, not the -fdebug maps,
         and also not even by the -ffile maps I suggested. This needs a
         proper look at GCC, I suspect it's outputting an unmapped path.
 
       * The "comp" set has differences, where (full) source filenames
         show up in the binaries (lto-dump, cc1, cc1obj cc1objplus,
         cc1plus, lto1)
 
 
 So to keep object files out of the source tree, -M or -O may be used.
 With -P active, -O must not be used, while -M is okay. This needs at
 least a docs update, forbid -O with -P in build.sh, or apply the
 suggested patch to make it work. With the patch and when using -M, the
 only remaining differences (wrt. embedded pathes) are in the "tests"
 set for the ubsan testcases.
 
 MfG, JBG
 
 --=20
 
 --hi5gnoo3wgobr4uk
 Content-Type: application/pgp-signature; name="signature.asc"
 
 -----BEGIN PGP SIGNATURE-----
 
 iFwEABECAB0WIQQlDTvPcScNjKREqWEdvV51g5nhuwUCZIuNyQAKCRAdvV51g5nh
 u0IOAJi+FXZg9jMz8WiaZ6+MKP0Iy3HmAJsGviN4ukEq5cjMm5xMQZYJLUdo3g==
 =gC+U
 -----END PGP SIGNATURE-----
 
 --hi5gnoo3wgobr4uk--