public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Sylvain Noiry <snoiry@kalrayinc.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: gcc@gcc.gnu.org, Paul Iannetta <piannetta@kalrayinc.com>,
	Benoit Dinechin <bddinechin@kalrayinc.com>
Subject: Re: [RFC] Exposing complex numbers to target backends
Date: Mon, 17 Jul 2023 09:18:32 +0000	[thread overview]
Message-ID: <MR2P264MB0113F52C7944ADBA52EB473FCD3BA@MR2P264MB0113.FRAP264.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <MR2P264MB0113AE6F7E7F17D8FEA6345DCD2CA@MR2P264MB0113.FRAP264.PROD.OUTLOOK.COM>

Hi,
  
> [...]
> You can find my code in this repo "https://github.com/ElectrikSpace/gcc.git"
> The implementation was originally done against the main dev branch of the KVX port,
> and the working proof of concept is located in the "complex/kvx" branch.
> I've also tried to apply the patch of GCC master branch today, with a minimal
> adaptation of the x86 backend, in "the complex/x86" branch.
> Both branches have the same generic patch (that I will split later) plus a backend
> specific patch. I'm a little bit lost in the x86 backend, so it's not very usable
> for now, but I will work on it.

I have sent a little bit earlier a series of patches which describes my
implementation of the support for native complex operations. There are
8 generic patches and 1 experimental x86 patch which exploits a portion
of the added features.

The initial message called "[PATCH 0/9] Native complex operations" [1] explains the
implementation details and illustrate it with some examples, mainly on KVX because
the backend implements all the features and the ISA has native complex instructions.
Some implementation details need to be discussed, especially concerning vectors
of complex elements and the merge with the work from Arm.

[1] : "https://gcc.gnu.org/pipermail/gcc-patches/2023-July/624644.html"

Best regards,
Sylvain








  reply	other threads:[~2023-07-17  9:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-05 15:12 Sylvain Noiry
2023-07-05 18:10 ` Toon Moene
2023-07-06 11:02 ` Richard Biener
2023-07-06 15:04   ` Sylvain Noiry
2023-07-17  9:18     ` Sylvain Noiry [this message]
2023-09-12 10:12       ` 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=MR2P264MB0113F52C7944ADBA52EB473FCD3BA@MR2P264MB0113.FRAP264.PROD.OUTLOOK.COM \
    --to=snoiry@kalrayinc.com \
    --cc=bddinechin@kalrayinc.com \
    --cc=gcc@gcc.gnu.org \
    --cc=piannetta@kalrayinc.com \
    --cc=richard.guenther@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).