From: Andrew Pinski <pinskia@gmail.com>
To: Toon Moene <toon@moene.org>
Cc: gcc mailing list <gcc@gcc.gnu.org>, fortran@gcc.gnu.org
Subject: Re: Tests of gcc development beyond its testsuite (in this case, for gfortran)
Date: Mon, 6 May 2024 14:32:57 -0700 [thread overview]
Message-ID: <CA+=Sn1mJSEF6h4zwVXa0oVWaChbF=PQ486zzb7TG6WrBgPdNaQ@mail.gmail.com> (raw)
In-Reply-To: <2299c71f-5e16-4cbd-bcd6-aadbdb1f7367@moene.org>
On Mon, May 6, 2024 at 2:27 PM Toon Moene <toon@moene.org> wrote:
>
> I have now, for some time, ran LAPACK's test programs on my gcc/gfortran
> builds on both on the x86_64-linux-gnu architecture, as well as the
> aarch64-linux-gnu one (see, e.g.,
> http://moene.org/~toon/lapack-amd64-gfortran13-O3).
>
> The results are rather alarming - this is r15-202 for aarch64 vs r15-204
> for x86_64 (compiled with -O3):
Did you test x86_64 with -march=native (or with -mfma) or just -O3?
The reason why I am asking is aarch64 includes FMA by default while
x86_64 does not.
Most recent x86_64 includes an FMA instruction but since the base ISA
does not include it, it is not enabled by default.
I am suspect the aarch64 "excessive exceeding the threshold for
errors" are all caused by the more use of FMA rather than anything
else.
Thanks,
Andrew Pinski
>
> diff lapack-amd64-gfortran15-O3 lapack-aarch64-gfortran15-O3
>
> 3892,3895c3928,3931
> < REAL 1327023 0 (0.000%) 0 (0.000%)
> < DOUBLE PRECISION 1300917 6 (0.000%) 0 (0.000%)
> < COMPLEX 786775 0 (0.000%) 0 (0.000%)
> < COMPLEX16 787842 0 (0.000%) 0 (0.000%)
> ---
> > REAL 1317063 71 (0.005%) 0 (0.000%)
> > DOUBLE PRECISION 1318331 54 (0.004%) 4 (0.000%)
> > COMPLEX 767023 390 (0.051%) 0 (0.000%)
> > COMPLEX16 772338 305 (0.039%) 0 (0.000%)
> 3897c3933
> < --> ALL PRECISIONS 4202557 6 (0.000%) 0 (0.000%)
> ---
> > --> ALL PRECISIONS 4174755 820 (0.020%) 4 (0.000%)
>
> Note the excessive exceeding the threshold for errors on the aarch64
> side (>).
>
> Of course, this is only an excerpt of the full log file - there is more
> information in it to zoom in on the errors on the aarch64 side (note
> that the x86_64 side is not faultless).
>
> Is there a way to pass this information to our websites, so that we do
> not "forget" this - or in the alternative, follow the progress in
> solving this ?
>
> Kind regards,
>
> --
> Toon Moene - e-mail: toon@moene.org - phone: +31 346 214290
> Saturnushof 14, 3738 XG Maartensdijk, The Netherlands
next prev parent reply other threads:[~2024-05-06 21:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 21:27 Toon Moene
2024-05-06 21:32 ` Andrew Pinski [this message]
2024-05-06 21:35 ` Toon Moene
2024-05-06 22:02 ` Toon Moene
2024-05-07 18:30 ` Toon Moene
2024-05-07 18:35 ` Andrew Pinski
2024-05-07 18:44 ` Toon Moene
2024-05-08 12:43 ` Toon Moene
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+=Sn1mJSEF6h4zwVXa0oVWaChbF=PQ486zzb7TG6WrBgPdNaQ@mail.gmail.com' \
--to=pinskia@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=toon@moene.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).