aboutsummaryrefslogtreecommitdiff
path: root/gcc/rust/util/rust-attribute-values.h
diff options
context:
space:
mode:
authorSandra Loosemore <sloosemore@baylibre.com>2025-04-03 02:40:59 +0000
committerSandra Loosemore <sloosemore@baylibre.com>2025-04-03 02:56:05 +0000
commit4590a31f81ae18e0d887c1a56f510d22754f31ed (patch)
treec89187a14abdb344cad938d44b3589338f6b7472 /gcc/rust/util/rust-attribute-values.h
parent93acd068af65c4a73ddaee6a8e36f016bde3df9d (diff)
downloadgcc-4590a31f81ae18e0d887c1a56f510d22754f31ed.zip
gcc-4590a31f81ae18e0d887c1a56f510d22754f31ed.tar.gz
gcc-4590a31f81ae18e0d887c1a56f510d22754f31ed.tar.bz2
Doc: Clarify use of access attribute [PR101440]
This issue was specifically about a confusing mention of the "second and third arguments to the memcpy function" when only the second one is a pointer affected by the attribute, but reading through the entire discussion I found other things confusing as well; e.g. in some cases it wasn't clear whether the "arguments" were the arguments to the attribute or the function, or exactly what a "positional argument" was. I've tried to rewrite that part to straighten it out, as well as some light copy-editing throughout. gcc/ChangeLog PR c/101440 * doc/extend.texi (Common Function Attributes): Clean up some confusing language in the description of the "access" attribute.
Diffstat (limited to 'gcc/rust/util/rust-attribute-values.h')
0 files changed, 0 insertions, 0 deletions