On 12/22/2025 11:06 AM, Sandra Loosemore wrote:
Continuing my work on PR122243, I found that there were several RISC-V
options that were not documented at all, and that the autogenerated
table of supported extensions had formatting issues as well as many
entries missing documentation. Since I had to synthesize a lot of
text for these patches, I'd like to get approval or corrections from
an actual target maintainer before pushing them.
Also, a caveat: while I think all my changes to the .def files were
confined to documentation strings and I was able to build GCC for a
riscv64-unknown-elf target in order to regenerate riscv-ext.texi, I
have no RISC-V test environment set up presently for regression
testing so I did not do that. :-S
I'll add a separate "make regenerate-opt-urls" commit once these are
approved and ready to go. Also, PR112650 (documenting the RISC-V
parameters) is still in my queue and not addressed by either of these
patches.
-Sandra
Sandra Loosemore (2):
doc, riscv: Clean up documentation of RISC-V options [PR122243]
doc, riscv: Clean up RISC-V extensions documentation
These patches are fine. Note that we have a pre-commit tester which
monitors this list and will handle testing. Your patch:
https://patchwork.sourceware.org/project/gcc/patch/[email protected]/
The lint check did find a case where we don't have two spaces after a
period:
=== ERROR type #1: dot, space, space, new sentence (2 error(s)) ===
gcc/doc/invoke.texi:32025:63:The subsequent part of the string is a list
of extension names.█Extension
gcc/doc/invoke.texi:32030:53:An underscore can appear anywhere after the
base ISA.█It has no specific
Those may have been pre-existing and just triggered because they're part
of the context for your changes. I didn't check that explicitly. The
other two lint things appear "normal" to me in texi code. and .opt stuff.
Jeff
jeff
