This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFC PATCH V2 00/10] port C-SKY to glibc


On 04/08/2018 10:29 AM, Mao Han wrote:
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

It's still not clear to me whether you intend to support more than one ABI (there is a __CSKYABIV2__ preprocessor conditional in the submission, for example).

If you support multiple ABIs, won't you need different target triplets?

Thanks,
Florian


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]