From: Paolo Carlini <pcarlini@suse.de>
To: gcc@gcc.gnu.org
Subject: Gcc complex division (default) algorithm
Date: Tue, 07 Dec 2004 13:59:00 -0000 [thread overview]
Message-ID: <41B5B781.2010602@suse.de> (raw)
Hi everyone,
I would ask you to have a brief look to the recent messages in gcc-bugs
named *complex numbers: basically, it turns out that, by default (that
is, when flag_complex_divide_method == 0) we are using a ""naive"" algo
for complex division.
Now, I can definitely understand that the "improved" algorithm, already
implemented (see expand_complex_div_wide in gcc/tree-complex.c) is more
costly, but would like to know the rationale of the choice, its history,
future plans (C99?): comments are very welcome!
Thank you in advance,
Paolo.
reply other threads:[~2004-12-07 13:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=41B5B781.2010602@suse.de \
--to=pcarlini@suse.de \
--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).