From: Paul Iannetta <piannetta@kalrayinc.com>
To: binutils@sourceware.org
Cc: Paul Iannetta <piannetta@kalrayinc.com>
Subject: [PATCH 0/7] kvx: New port.
Date: Fri, 21 Jul 2023 09:49:49 +0200 [thread overview]
Message-ID: <20230721074956.7188-1-piannetta@kalrayinc.com> (raw)
On behalf of Kalray - a semiconductor company based in the south of France - I
would like to contribute the binutils port for the KVX ISA, with the following
sub-architectures:
- kv3-v1: 3rd gen (Coolidge), 1st revision (stable);
- kv3-v2: 3rd gen (Coolidge), 2nd revision (stable);
- kv4-v1: 4th gen (Dolomites), 1st revision (experimental).
I will be the maintainer of the port.
I've split up the port into as many parts as subdirectories we have changes in,
the current set of patch covers the binutils without gdb (that we plan to upstream
in a second time.)
Kalray has completed the copyright assignment forms from FSF for the binutils.
Please let me know if I am missing anything.
Regards,
Paul Iannetta,
Kalray
next reply other threads:[~2023-07-21 7:50 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 7:49 Paul Iannetta [this message]
2023-07-21 7:49 ` [PATCH 1/7] kvx: Add bf files Paul Iannetta
2023-07-21 7:49 ` [PATCH 2/7] kvx: Add binutils files Paul Iannetta
2023-07-21 7:49 ` [PATCH 3/7] kvx: Add gas file Paul Iannetta
2023-07-21 7:49 ` [PATCH 4/7] kvx: Add ld files Paul Iannetta
2023-07-21 7:49 ` [PATCH 5/7] kvx: Add include files Paul Iannetta
2023-07-21 7:49 ` [PATCH 6/7] kvx: Add opcodes file Paul Iannetta
2023-07-21 7:49 ` [PATCH 7/7] kvx: Add toplevel files Paul Iannetta
2023-07-21 8:29 ` [PATCH 0/7] kvx: New port Nick Clifton
[not found] ` <20230721090932.pspnpq2q2wjnshrh@ws2202.lin.mbt.kalray.eu>
[not found] ` <2050791e-38ee-5719-037f-c03c456f3e3d@redhat.com>
2023-07-21 16:47 ` Paul Iannetta
2023-07-21 17:00 ` Paul Iannetta
2023-07-21 8:57 ` YunQiang Su
2023-07-21 16:51 ` Paul Iannetta
2023-07-24 9:04 ` Nick Clifton
2023-07-24 9:38 ` Paul Iannetta
2023-07-24 9:28 ` Nick Clifton
2023-07-24 12:33 ` Paul Iannetta
2023-07-24 14:30 ` Paul Iannetta
2023-07-25 14:13 ` Nick Clifton
2023-07-26 7:36 ` Paul Iannetta
2023-07-26 13:32 ` Michael Matz
2023-07-26 21:46 ` Paul Iannetta
2023-07-26 21:24 ` [PATCH v2] " Paul Iannetta
2023-07-31 14:52 ` Nick Clifton
2023-08-02 14:38 ` [PATCH v3] " Paul Iannetta
2023-08-16 13:24 ` Nick Clifton
2023-08-17 9:45 ` Luis Machado
2023-08-17 15:09 ` Paul Iannetta
2023-08-17 16:28 ` Luis Machado
2023-08-17 23:20 ` Alan Modra
2023-08-18 7:13 ` Paul Iannetta
2023-08-17 12:46 ` Paul Iannetta
2023-07-24 9:53 ` [PATCH 0/7] " Nick Clifton
2023-07-24 12:27 ` Paul Iannetta
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=20230721074956.7188-1-piannetta@kalrayinc.com \
--to=piannetta@kalrayinc.com \
--cc=binutils@sourceware.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).