On Mon, 3 Jun 2024, Tobias Burnus wrote: > Richard Biener wrote: > > On Mon, 3 Jun 2024, Tobias Burnus wrote: > >> Thomas Schwinge wrote: > >>> In the following, I have then reconsidered that stance; we may actually > >>> "Implement global constructor, destructor support in a conceptually > >>> simpler way than using 'collect2' (the program): implement the respective > >>> functionality in the nvptx-tools 'ld'". The latter is > >>> > >>> "ld: Global constructor/destructor support". > >> The attached patch makes clearer which version should be > >> installed by recommending this patch (= latest nvptx-tools) > >> in install.texi. > > Can we simply say "newerst" where I guess refering to a github repo > > already implies this? > > Good question. The problem I see with just referring to a repository (even > with newest) often means: yes, that software I have (whatever version). While > if some reference goes to a 2024 version, I might not know what version I have > but likely an older version → I will update. > > Admittedly, as people tend to *not* read the documentation, this approach > might fail as well. But, maybe, it is sufficient to update GCC 15's release > notes?* > > It won't help those not reading with the release notes before building and the > wording* had to be changed a bit as install.texi no longer states what version > should be used, but it would be an alternative install.texi also has the issue that it's not pre-packaged in a easy to discover and readable file in the release tarballs and that the online version is only for trunk. > (*) https://gcc.gnu.org/pipermail/gcc-patches/2024-June/653417.html > > Tobias > > > -- Richard Biener SUSE Software Solutions Germany GmbH, Frankenstrasse 146, 90461 Nuernberg, Germany; GF: Ivo Totev, Andrew McDonald, Werner Knoblich; (HRB 36809, AG Nuernberg)