I added the following on top, originally triggered by spotting the missing space between "Function" and "Multi...", and observing that in our docs it says "Multiversioning", without dash.
Pushed. Gerald >From 7c7fe28a3a6879c5937b52c888b664c5cde42bea Mon Sep 17 00:00:00 2001 From: Gerald Pfeifer <[email protected]> Date: Sun, 20 Sep 2026 09:35:23 +0200 Subject: [PATCH] gcc-16: Editorial changes for LoongArch --- htdocs/gcc-16/changes.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/htdocs/gcc-16/changes.html b/htdocs/gcc-16/changes.html index 25916f428..9068e6d22 100644 --- a/htdocs/gcc-16/changes.html +++ b/htdocs/gcc-16/changes.html @@ -853,11 +853,11 @@ struct Affected : E <li>Bit-precise integer types (<code>_BitInt (<i>N</i>)</code> and <code>unsigned _BitInt (<i>N</i>)</code>) are supported. </li> - <li>Added FunctionMulti-Versioning (FMV) support. The + <li>Added Function Multiversioning (FMV) support. The <a href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/gcc/LoongArch-Attributes.html#index-target_005fclones_002c-LoongArch";><code>target_clones</code></a> attribute can be used to generate multiple function versions for different LoongArch CPU features - (e.g., <code>lsx</code>, <code>lasx</code>), with automatic + (e.g., <code>lsx</code> and <code>lasx</code>), with automatic runtime selection of the optimal version based on CPU capabilities. </li> <li>Added support for the LoongArch32 architecture, including the -- 2.55.0
