Hi Gerald, > On 7 Jul 2024, at 19:26, Gerald Pfeifer <ger...@pfeifer.com> wrote: > > External email: Use caution opening links or attachments > > > On Tue, 2 Apr 2024, Kyrylo Tkachov wrote: >> Here's a writeup of the AArch64 changes to highlight in GCC 14.1. If >> there's something you'd like to highlight feel free to comment or add a >> patch yourself. I don't expect the list to be exhaustive. >> >> It's been a busy release for AArch64! > > Indeed. Busy in a good way. :-) > > How about the following simplification around generic-armv8-a and > generic-armv8-a? I believe this version is easier to consume. >
Yeah, that does look smoother. Ok. Thanks! Kyrill > (_Not_ pushed.) > > Gerald > > > diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html > index 9a1b0c8a..ca4cae0f 100644 > --- a/htdocs/gcc-14/changes.html > +++ b/htdocs/gcc-14/changes.html > @@ -687,11 +687,11 @@ You may also want to check out our > <li>Microsoft Cobalt-100 (<code>cobalt-100</code>).</li> > </ul></li> > <li>Additionally, the identifiers <code>generic</code>, > - <code>generic-armv8-a</code> and <code>generic-armv9-a</code> are added > - as arguments to <code>-mcpu=</code> and <code>-mtune=</code> to optimize > - code generation aimed at a good blend of CPUs of a particular > architecture > - version. These tunings are also used as the default optimization targets > - when compiling with the <code>-march=armv8-a</code> or > + <code>generic-armv8-a</code> and <code>generic-armv9-a</code> can be > + used to optimize code generation for a good blend of CPUs of a > + particular architecture > + version. These tunings are also used as the default optimization > + targets when compiling with the <code>-march=armv8-a</code> or > <code>-march=armv9-a</code> options and their point releases e.g. > <code>-march=armv8.2-a</code> or <code>-march=armv9.3-a</code>.</li> >
