From: Richard Biener <richard.guenther@gmail.com>
To: Jeff Law <jeffreyalaw@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH]middle-end Use subregs to expand COMPLEX_EXPR to set the lowpart.
Date: Mon, 13 Jun 2022 13:54:44 +0200 [thread overview]
Message-ID: <CAFiYyc0FM7OnbCb5M0=3x24N1_1cDS8wSkWFXZxCcxqn98tKZQ@mail.gmail.com> (raw)
In-Reply-To: <c296bc75-c730-f2bb-45d0-8ccfd0b2cfc0@gmail.com>
On Sun, Jun 12, 2022 at 7:27 PM Jeff Law via Gcc-patches
<gcc-patches@gcc.gnu.org> wrote:
[...]
> On a related topic, any thoughts on keeping complex objects as complex
> types/modes through gimple and into at least parts of the RTL pipeline?
>
> The way complex arithmetic instructions work on our chip is going to be
> extremely tough to utilize in GCC -- we really need to the complex
> types/arithmetic up through RTL generation at the least. Ideally we'd
> even expose complex modes all the way to final. Is that something
> y'all could benefit from as well? Have y'all poked at this problem at all?
Since you are going to need to "recover" complex operations from people
open-coding them (both fortran and C and also C++ with std::complex) it
should be less work to just do that ;) I think that complex modes and types
exist solely for ABI purposes.
Richard.
> jeff
>
next prev parent reply other threads:[~2022-06-13 11:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 7:52 Tamar Christina
2022-06-12 17:27 ` Jeff Law
2022-06-13 10:19 ` Tamar Christina
2022-06-13 17:42 ` Jeff Law
2022-06-13 11:54 ` Richard Biener [this message]
2022-06-13 17:34 ` Jeff Law
2022-06-15 11:36 ` Richard Sandiford
2022-06-16 11:22 ` Tamar Christina
2022-06-24 21:54 ` Jeff Law
2022-06-13 8:40 ` Richard Sandiford
2022-06-16 11:28 ` Tamar Christina
2022-06-17 17:13 ` Richard Sandiford
2022-06-20 8:00 ` Richard Sandiford
2022-07-05 15:05 ` Tamar Christina
2022-07-05 16:11 ` Richard Sandiford
2022-08-29 10:52 ` Richard Biener
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='CAFiYyc0FM7OnbCb5M0=3x24N1_1cDS8wSkWFXZxCcxqn98tKZQ@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
/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).