On 8/31/25 03:56, Jonathan Wakely wrote:
On Sun, 31 Aug 2025 at 10:48 +0100, Jonathan Wakely wrote:
Grr, we also have:
unavailable
unused
used
retain
uninitialized
I can kinda understand unused, used, and retain being grouped together
(although cross-references are a thing) but they should not all be
ordered before uninitialized.
I think it's better to keep the list alphabetized, and add the
cross-references.
And what is an "OSABI" in the description of retain?!
https://gcc.gnu.org/onlinedocs/gcc-15.2.0/gcc/Common-Variable-
Attributes.html#index-retain-variable-attribute
My suggestion is to rewrite that as
This attribute saves the variable from linker garbage collection.
[...rest of existing para...]
This additional functionality requires linker support for the ELF
@code{SHF_GNU_RETAIN} flag, e.g. GNU Binutils version 2.36 or later.
The function attribute description needs similar editing.
BTW, I already have a documentation project in mind for GCC 16 to revise
the entire presentation of GCC attributes. Now that the default dialect
for both C and C++ supports the standard attribute syntax, we should be
using that in the manual (PR102397). And there are now so many
attributes that it makes sense to introduce a new section for
symbol/declaration attributes that apply to both functions and variables
(PR88472). Probably I will not have time to tackle this until late in
stage 3 or stage 4, though.... if anybody else wants to undertake any
improvements meanwhile, go ahead!
-Sandra
