From: Martin Uecker <uecker@tugraz.at>
To: Richard Biener <richard.guenther@gmail.com>, Toon Moene <toon@moene.org>
Cc: gcc mailing list <gcc@gcc.gnu.org>
Subject: Re: Complex numbers in compilers - upcoming GNU Tools Cauldron.
Date: Tue, 12 Sep 2023 13:12:57 +0200 [thread overview]
Message-ID: <0bcfbb7c065266c1bcd3d14da0ec588691beffe2.camel@tugraz.at> (raw)
In-Reply-To: <CAFiYyc2XiZF_96MayieTQF5BmrUeuuKdnczA5Cp_WOnkb57H7A@mail.gmail.com>
Am Dienstag, dem 12.09.2023 um 11:25 +0200 schrieb Richard Biener via Gcc:
> On Tue, Sep 5, 2023 at 10:44 PM Toon Moene <toon@moene.org> wrote:
> >
> > 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.
>
> Lack of applications / benchmarks using complex numbers is also a
> problem for any work on this.
>
I could probably provide some examples such as a FFT,
complex Gaussian random number generation, mandelbrot
set computation, etc.
Martin
next prev parent reply other threads:[~2023-09-12 11:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 20:43 Toon Moene
2023-09-12 9:25 ` Richard Biener
2023-09-12 11:12 ` Martin Uecker [this message]
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=0bcfbb7c065266c1bcd3d14da0ec588691beffe2.camel@tugraz.at \
--to=uecker@tugraz.at \
--cc=gcc@gcc.gnu.org \
--cc=richard.guenther@gmail.com \
--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).