[Bug libstdc++/116657] tzdata 2024b causing timezone parsing issues in std::chrono

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116657 --- Comment #12 from Toolybird --- Thank you very much for the speedy response!

[Bug libstdc++/116657] tzdata 2024b causing timezone parsing issues in std::chrono

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116657 --- Comment #7 from Toolybird --- >From the 2024b release announcement at https://lists.iana.org/hyperkitty/list/tz-annou...@iana.org/thread/IZ7AO6WRE3W3TWBL5IR6PMQUL433BQIE/ "The main data form now uses %z."

[Bug libstdc++/116657] New: tzdata 2024b causing timezone parsing issues in std::chrono

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116657 Bug ID: 116657 Summary: tzdata 2024b causing timezone parsing issues in std::chrono Product: gcc Version: 14.2.1 Status: UNCONFIRMED Severity: normal

[Bug go/104832] gccgo / libgo Reproducibility Problem

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104832 --- Comment #7 from Toolybird --- I just stumbled across this openSUSE bug report which may or may not be related: https://bugzilla.opensuse.org/show_bug.cgi?id=1188621 Interesting that it mentions filesystem readdir which I hadn't considered

[Bug go/104832] gccgo / libgo Reproducibility Problem

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104832 --- Comment #6 from Toolybird --- Created attachment 52588 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52588&action=edit archive/zip.o differences

[Bug go/104832] gccgo / libgo Reproducibility Problem

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104832 --- Comment #5 from Toolybird --- Created attachment 52587 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52587&action=edit image/gif.o differences No worries. I'm attaching 2 diffs pertaining to "image/gif.o" and "archive/zip.o". Thanks

[Bug go/104832] gccgo / libgo Reproducibility Problem

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104832 --- Comment #3 from Toolybird --- Thanks for the quick patch! Things are a bit different now but unfortunately the problem persists. It appears there is an element of randomness to this problem as the list of affected object files has changed.

[Bug go/104832] New: gccgo / libgo Reproducibility Problem

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104832 Bug ID: 104832 Summary: gccgo / libgo Reproducibility Problem Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: go

[Bug go/101407] non-determinism in -fdump-go-spec

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101407 --- Comment #4 from Toolybird --- Your patch solves the problem for me. Thank you very much!

[Bug go/101407] non-determinism in -fdump-go-spec

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101407 --- Comment #2 from Toolybird --- > Will try to bisect Well, that was a complete waste of time. There seems to an element of randomness to the problem. It turns out that GCC 10 is also affected as I was able to trigger it all the way back to b

[Bug go/101407] non-determinism in -fdump-go-spec

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101407 --- Comment #1 from Toolybird --- The bug is present on trunk. Will try to bisect...

[Bug go/101407] New: non-determinism in -fdump-go-spec

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101407 Bug ID: 101407 Summary: non-determinism in -fdump-go-spec Product: gcc Version: 11.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: go

[Bug driver/101383] GCC 11 Reproducibility Issue

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101383 --- Comment #6 from Toolybird --- The patch you posted to gcc-patches solves my problem. Thank you for the quick fix!

[Bug other/101383] New: GCC 11 Reproducibility Issue

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101383 Bug ID: 101383 Summary: GCC 11 Reproducibility Issue Product: gcc Version: 11.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: other A