From: Toon Moene <toon@moene.org>
To: gcc@gcc.gnu.org
Cc: gfortran <fortran@gcc.gnu.org>
Subject: Re: Complex numbers support: discussions summary
Date: Thu, 5 Oct 2023 16:45:05 +0200 [thread overview]
Message-ID: <a7f846f5-a3c6-4220-a0ac-8927cd876c99@moene.org> (raw)
In-Reply-To: <87d8389c-3ff5-45ed-bc5e-19463564d703@moene.org>
On 9/26/23 20:40, Toon Moene wrote:
> On 9/26/23 09:30, Richard Biener via Gcc wrote:
>
>> On Mon, Sep 25, 2023 at 5:17 PM Sylvain Noiry via Gcc
>> <gcc@gcc.gnu.org> wrote:
>
>>> As I said at the end of the presentation, we have written a paper which
>>> explains
>>> our implementation in details. You can find it on the wiki page of the
>>> Cauldron
>>> (https://gcc.gnu.org/wiki/cauldron2023talks?action=AttachFile&do=view&target=Exposing+Complex+Numbers+to+Target+Back-ends+%28paper%29.pdf).
>>
>> Thanks for the detailed presentation at the Cauldron.
>>
>> My personal summary is that I'm less convinced delaying lowering is
>> the way to go.
>
> Thanks Sylvain for the quick summary of the discussion - it helps a
> great deal now that the discussion is still fresh in our memory.
I found time today to run some tests.
First of all, the result of the gcc test harness as applied to the top
of the complex/kvx branch in the https://github.com/kalray/gcc repository:
https://gcc.gnu.org/pipermail/gcc-testresults/2023-October/797627.html
I think there are several complex failures here that are not in
"standard" 12.2 release (for x86_64-linux-gnu).
I also compiled all of lapack-3.11.0 with that compiler and obtained the
same results as with gcc/gfortran 13.2:
--> LAPACK TESTING SUMMARY <--
Processing LAPACK Testing output found in the TESTING directory
SUMMARY nb test run numerical error other error
================ =========== ================= ================
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%)
--> ALL PRECISIONS 4202557 6 (0.000%) 0 (0.000%)
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:[~2023-10-05 14:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 15:15 Sylvain Noiry
2023-09-26 7:30 ` Richard Biener
2023-09-26 8:29 ` Tamar Christina
2023-09-26 10:19 ` Paul Iannetta
2023-09-26 8:53 ` Paul Iannetta
2023-09-26 9:28 ` Tamar Christina
2023-09-26 9:40 ` Paul Iannetta
2023-09-26 18:40 ` Toon Moene
2023-10-05 14:45 ` Toon Moene [this message]
2023-09-26 15:46 ` Joseph Myers
-- strict thread matches above, loose matches on Subject: below --
2023-10-16 9:14 Sylvain Noiry
2023-10-17 20:37 ` Toon Moene
2023-10-18 7:24 ` Sylvain Noiry
2023-10-09 13:29 Sylvain Noiry
2023-09-25 14:56 Sylvain Noiry
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=a7f846f5-a3c6-4220-a0ac-8927cd876c99@moene.org \
--to=toon@moene.org \
--cc=fortran@gcc.gnu.org \
--cc=gcc@gcc.gnu.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).