public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Sandra Loosemore <sandra@codesourcery.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: Han Mao <han_mao@c-sky.com>, Yunhai Shang <yunhai_shang@c-sky.com>
Subject: [0/5] C-SKY port
Date: Tue, 24 Jul 2018 04:17:00 -0000	[thread overview]
Message-ID: <49d0a2c8-51a0-4a74-d015-0bf1c1098e38@codesourcery.com> (raw)

This patch series is a new port for C-SKY ABI V2 processors.  It's
based on the original work by C-SKY with cleanup, modernization, and
bug-fixing by Mentor Graphics.  The supported targets are csky-elf and
csky-linux-* (both glibc and uClibc).  At this time we're only
supporting the C and C++ languages, but we've built all the other
front ends except Ada where we're still trying to sort out build
environment issues.

C-SKY proposes Han Mao <han_mao@c-sky.com> and Yunhai Shang
<yunhai_shang@c-sky.com> as maintainers for this port.  We expect that
C-SKY will also be providing a public link to the processor and ABI
documentation at some point.  Meanwhile, here's brief overview
of the architecture from the compiler's point of view:

This is a 32-bit target with mixed 16- and 32-bit instructions and
support for both endiannesses.  There are 5 different architecture
variants.  The ck801 variant is substantially different from the
others in terms of code generation -- it has only a few 32-bit
instructions and a restricted register set, so it's almost analagous
to a Thumb-only ARM core.  ck802 and ck803 have more 32-bit
instructions and 16 registers, while ck807 and ck810 are Linux-capable
with 32 registers.

The ABI is fairly standard; arguments are passed in r0-r3 with the
overflow on the stack, return values in r0-r1, etc.  There is no
dedicated frame pointer register.

The ELF target is configured to build 16(!) multilibs and the Linux
targets 8, to account for hard/soft float variants and endiannesses.
We've been testing all of them with QEMU (user-mode for the Linux
targets, since we don't have a stable kernel yet) and the results are
quite good now.

I've split the patch set up into 5 pieces, with part 2 having the bulk
of the new code:

[1] Configury
[2] Backend implementation
[3] Documentation
[4] Testsuite
[5] libgcc

We also have a couple small patches to target-independent code to fix
bugs, which we'll post separately.

-Sandra

             reply	other threads:[~2018-07-24  4:17 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-24  4:17 Sandra Loosemore [this message]
2018-07-24  4:20 ` [1/5] C-SKY port: Configury Sandra Loosemore
2018-07-24 15:09   ` Jeff Law
2018-07-24  4:21 ` [2/5] C-SKY port: Backend implementation Sandra Loosemore
2018-07-24 15:45   ` Jeff Law
2018-07-24 18:19     ` Sandra Loosemore
2018-07-24 21:25       ` Jeff Law
2018-07-25  0:17         ` Sandra Loosemore
2018-07-25  4:50           ` Jeff Law
2018-07-25 13:17             ` Paul Koning
2018-07-25 14:54               ` Sandra Loosemore
2018-07-26  6:07         ` 瞿仙淼
2018-07-28  1:49           ` Sandra Loosemore
2018-08-02 22:33             ` Jeff Law
2018-08-02 22:28           ` Jeff Law
2018-08-03  7:58             ` Yunhai
2018-08-03 16:26             ` Sandra Loosemore
2018-07-24  4:23 ` [3/5] C-SKY port: Documentation Sandra Loosemore
2018-07-24 15:10   ` Jeff Law
2018-07-24  4:25 ` [4/5] C-SKY port: Testsuite Sandra Loosemore
2018-07-24 15:10   ` Jeff Law
2018-07-24  4:26 ` [5/5] C-SKY port: libgcc Sandra Loosemore
2018-07-24 15:12   ` Jeff Law
2018-07-24 18:10   ` Segher Boessenkool
2018-07-24 18:19     ` Sandra Loosemore
2018-07-24 19:46       ` Segher Boessenkool
2018-07-24 15:23 ` [0/5] C-SKY port Sandra Loosemore
2018-07-26 23:04   ` Joseph Myers
2018-07-30 16:59     ` Sandra Loosemore
2018-08-01 14:28     ` 瞿仙淼

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=49d0a2c8-51a0-4a74-d015-0bf1c1098e38@codesourcery.com \
    --to=sandra@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=han_mao@c-sky.com \
    --cc=yunhai_shang@c-sky.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).