http://bugzilla.opensuse.org/show_bug.cgi?id=1040589 Bernhard Wiedemann changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |1081754 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1040589 http://bugzilla.opensuse.org/show_bug.cgi?id=1040589#c9 Martin Liška changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |martin.liska@suse.com --- Comment #9 from Martin Liška --- So I did analysis of 2 packages before the changes in Factory happened: 1) gzip - as mentioned a temp file was used and zipped. Temp file name probably causes the divergence as it's always different. 2) sed - it uses pthreads (but not passed as CFLAGS), thus I added -fprofile-update=atomic to cflags. See documentation here: https://gcc.gnu.org/onlinedocs/gcc/Instrumentation-Options.html and I've got it, diff in between 2 runs: ./gnulib-tests/nanosleep.gcda: a3000000: 37:PROGRAM_SUMMARY checksum=0x99d0fa93 [snip] ./gnulib-tests/nanosleep.gcda: 01a10000: 14:COUNTERS arcs 7 counts ./gnulib-tests/nanosleep.gcda: 0 2 1 1 0 1 29 30 ./gnulib-tests/nanosleep.gcda: a3000000: 37:PROGRAM_SUMMARY checksum=0xc3046d04 [snip] ./gnulib-tests/nanosleep.gcda: 0 2 1 1 0 1 30 31 ./lib/stat-time.h: stat_time_normalize (int result, struct stat *st _GL_UNUSED) { #if defined __sun && defined STAT_TIMESPEC if (result == 0) { long int timespec_resolution = 1000000000; short int const ts_off[] = { offsetof (struct stat, st_atim), offsetof (struct stat, st_mtim), offsetof (struct stat, st_ctim) }; int i; for (i = 0; i < sizeof ts_off / sizeof *ts_off; i++) { struct timespec *ts = (struct timespec *) ((char *) st + ts_off[i]); long int q = ts->tv_nsec / timespec_resolution; long int r = ts->tv_nsec % timespec_resolution; if (r < 0) { r += timespec_resolution; q--; } ts->tv_nsec = r; /* Overflow is possible, as Solaris 11 stat can yield tv_sec == TYPE_MINIMUM (time_t) && tv_nsec == -1000000000. INT_ADD_WRAPV is OK, since time_t is signed on Solaris. */ if (INT_ADD_WRAPV (q, ts->tv_sec, &ts->tv_sec)) { errno = EOVERFLOW; return -1; } } } #endif return result; } It loops based on how fast time flies. This can't be stable. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1040589 http://bugzilla.opensuse.org/show_bug.cgi?id=1040589#c11 Martin Liška changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS Assignee|rguenther@suse.com |martin.liska@suse.com --- Comment #11 from Martin Liška --- I've done https://build.opensuse.org/request/show/597754 Then we can check the packages and eventually revert the changes that were done as a workaround. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1040589 http://bugzilla.opensuse.org/show_bug.cgi?id=1040589#c44 --- Comment #44 from Andreas Stieger --- (In reply to Bernhard Wiedemann from comment #43)

bison-3.7.3 started to vary from PGO.

Can you help me understand if this is a (new) problem in 3.7.3, and give the steps to compare the binaries? Last I found was: http://rb.zq1.de/compare.factory-20200430/bison-compare.out -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1040589 http://bugzilla.opensuse.org/show_bug.cgi?id=1040589#c46 --- Comment #46 from Martin Pluskal --- (In reply to Bernhard Wiedemann from comment #45)

I found my debugging note from/before 2020-06-29:

...

PGO again via ASLR, filesys, date

https://build.opensuse.org/request/show/676711 made it reproducible back then and looking closer at old results, 3.5.2 was the first one marked to differ https://rb.zq1.de/compare.factory-20200303/bison-compare.out

Here is the general description of the problem of PGO with reproducibility: https://github.com/bmwiedemann/theunreproduciblepackage/tree/master/pgo

Would disabling PGO for bison be an option?

No! I do not wish to damage speed and/or optimized size of binaries because of this. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1040589 http://bugzilla.opensuse.org/show_bug.cgi?id=1040589#c48 --- Comment #48 from Bernhard Wiedemann --- I dont think, this has been fully solved. gcc, bison, python all still suffer from PGO. I suspect bash-4.4 in 15.3 might also be affected. Maybe also MozillaFirefox. One intermediate solution would be to use in these .spec files %if 0%{?do_profiling} && !0%{?only_reproducible_profiling} -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1040589 Bernhard Wiedemann changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |1197575 -- You are receiving this mail because: You are on the CC list for the bug.