From: Mao Han <han_mao@c-sky.com>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: c-sky_gcc_upstream@c-sky.com, gnu-csky@mentor.com,
libc-alpha@sourceware.org
Subject: Re: [RFC PATCH V2 00/10] port C-SKY to glibc
Date: Sun, 08 Apr 2018 08:29:00 -0000 [thread overview]
Message-ID: <20180408082934.GA5215@vmh-VirtualBox> (raw)
In-Reply-To: <87efjq5e87.fsf@mid.deneb.enyo.de>
On Sun, Apr 08, 2018 at 09:50:16AM +0200, Florian Weimer wrote:
Hi,
> * Mao Han:
>
> > CK610 is the second-generation CPU of CSKY, fullycompatible with M*Core.
> > CK807/CK810 bases on C-SKY V2 instruction set architecture and 16/32-bit
> > variable length instruction. Including basic core(CK807/CK810),
> > floating-point enhancement(CK807F/CK810F), multimedia enhancement (CK810D)
> > and multiple-processing extension (CK807MP/CK810MP).
>
> Which ABIs of those do you intend to support?
>
> These should be added to the README file.
Thanks for comment.
In glibc and linux we only cares about following cpu and extensions.
ck610 only have: ck610
ck807 could have: ck807 ck807f ck807vf ck807ef
ck810 could have: ck810 ck810f ck810vf ck810ef
ck860 could have: ck860 ck860f ck860vf
f: means FPU co-processor
v: means VDSP co-processor just like "ARM-NEON"
e: is our old DSP co-processor which use HI-LO regs for operation. In
current ck807/ck810 they default have HI-LO regs.
For this patch-set, we support:
ck610
(ck807/ck807f/ck807ef)
(ck810/ck810e/ck810ef)
ck6** use csky-*-linux-gnuabiv1, ck8** use csky-*-linux-gnuabiv2
I will update the introduction for these.
It seems only this need be added to the README file. Is that correct?
csky-*-linux-gnuabi
Best Regards
Mao Han
next prev parent reply other threads:[~2018-04-08 8:29 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-08 7:03 Mao Han
2018-04-08 7:03 ` [RFC PATCH V2 01/10] C-SKY: ABI related code Mao Han
2018-04-17 20:53 ` Joseph Myers
2018-04-26 7:27 ` Mao Han
2018-04-08 7:03 ` [RFC PATCH V2 09/10] C-SKY: Linux Startup and Dynamic Loading Code Mao Han
2018-04-08 7:03 ` [RFC PATCH V2 08/10] C-SKY: Build Infastructure Mao Han
2018-04-08 7:41 ` Andreas Schwab
2018-04-16 5:59 ` Mao Han
2018-04-17 20:54 ` Joseph Myers
2018-04-08 7:03 ` [RFC PATCH V2 05/10] C-SKY: Atomic and Locking Routines Mao Han
2018-04-08 7:03 ` [RFC PATCH V2 07/10] C-SKY: ABI Lists Mao Han
2018-04-09 22:25 ` Rafal Luzynski
2018-04-10 0:59 ` Mao Han
2018-04-08 7:03 ` [RFC PATCH V2 03/10] C-SKY: Generic math Routines Mao Han
2018-04-08 7:03 ` [RFC PATCH V2 02/10] C-SKY: TLS support Mao Han
2018-04-17 20:50 ` Joseph Myers
2018-04-26 7:33 ` Mao Han
2018-04-26 16:00 ` Joseph Myers
2018-04-27 1:55 ` Guo Ren
2018-04-27 12:10 ` Joseph Myers
2018-04-29 8:49 ` Guo Ren
2018-04-08 7:03 ` [RFC PATCH V2 06/10] C-SKY: Linux Syscall Interface Mao Han
2018-04-15 20:29 ` Arnd Bergmann
2018-04-16 5:55 ` Mao Han
2018-04-23 11:32 ` Adhemerval Zanella
2018-04-26 7:39 ` Mao Han
2018-04-08 7:03 ` [RFC PATCH V2 04/10] C-SKY: Hard Float Support Mao Han
2018-04-08 7:04 ` [RFC PATCH V2 10/10] C-SKY: Linux ABI Mao Han
2018-04-17 20:56 ` Joseph Myers
2018-04-08 7:51 ` [RFC PATCH V2 00/10] port C-SKY to glibc Florian Weimer
2018-04-08 8:29 ` Mao Han [this message]
2018-04-09 8:43 ` Florian Weimer
2018-04-09 9:05 ` Mao Han
2018-04-17 20:44 ` Joseph Myers
[not found] ` <20180426072022.GA14714@vmh-VirtualBox>
2018-04-26 11:45 ` Joseph Myers
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=20180408082934.GA5215@vmh-VirtualBox \
--to=han_mao@c-sky.com \
--cc=c-sky_gcc_upstream@c-sky.com \
--cc=fw@deneb.enyo.de \
--cc=gnu-csky@mentor.com \
--cc=libc-alpha@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).