From: Toon Moene <toon@moene.org>
To: gcc mailing list <gcc@gcc.gnu.org>
Subject: Complex numbers in compilers - upcoming GNU Tools Cauldron.
Date: Tue, 5 Sep 2023 22:43:13 +0200 [thread overview]
Message-ID: <f3922268-7b27-4eff-ad16-f9bd77736c7d@moene.org> (raw)
This is going to be an interesting discussion.
In the upcoming GNU Tools Cauldron meeting the representation of complex
numbers in GCC will be discussed from the following "starting point":
"Complex numbers are used to describe many physical phenomenons and are
of prime importance in data signal processing. Nevertheless, despite
being part of the C and C++ standards since C99, they are still not
completely first class citizens in mainstream compilers."
*This* is from the Fortran 66 Standard (http://moene.org/~toon/f66.pdf -
a photocopy of the 1966 Standard):
- - - - -
Chapter 4. Data Types:
...
4.2.4 Complex Type.
A complex datum is processor approximation to the value of a complex number.
...
- - - - -
I can recall people complaining about the way complex arithmetic was
handled by compilers since the late 70s.
This is even obvious in weather forecasting software I have to deal with
*today* (all written in Fortran). Some models use complex variables to
encode the "spectral" (wave-decomposed) computations in parts where that
is useful - others just "degrade" those algorithms to explicitly use reals.
Kind regards,
--
Toon Moene - e-mail: toon@moene.org - phone: +31 346 214290
Saturnushof 14, 3738 XG Maartensdijk, The Netherlands
next reply other threads:[~2023-09-05 20:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 20:43 Toon Moene [this message]
2023-09-12 9:25 ` Richard Biener
2023-09-12 11:12 ` Martin Uecker
2023-09-12 13:31 ` Paul Koning
2023-09-12 18:36 ` 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=f3922268-7b27-4eff-ad16-f9bd77736c7d@moene.org \
--to=toon@moene.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).