From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Guillem Jover <guillem@debian.org>,
"980963@bugs.debian.org" <980963@bugs.debian.org>,
Alexey Brodkin <Alexey.Brodkin@synopsys.com>
Cc: linux-snps-arc <linux-snps-arc@lists.infradead.org>,
Helmut Grohne <helmut@subdivi.de>,
Claudiu Zissulescu <Claudiu.Zissulescu@synopsys.com>,
"debian-cross@lists.debian.org" <debian-cross@lists.debian.org>
Subject: Re: Bug#980963: dpkg: Please add ARC architecture
Date: Mon, 24 May 2021 20:41:23 +0000 [thread overview]
Message-ID: <4e8dbf4f-5e91-778f-7139-19a13e49ae4a@synopsys.com> (raw)
In-Reply-To: <6ca2d929-60d3-3846-876b-3b62dba635c0@synopsys.com>
Hi Guillem,
On 3/26/21 10:39 AM, Vineet Gupta wrote:
> On 3/4/21 3:56 PM, Vineet Gupta wrote:
>>> Also just to make sure, the GNU triplets are:
>>>
>>> arc-linux-gnu
>>> arceb-linux-gnu
>>> No ABI modifiers (stuff like “eabi”) for the libc part (“gnu“) right?
>> Actually it seems we are missing hardfloat here: ARC glibc/gcc support
>> it very well and should be default for any reasonable performance.
>>
>> So I think we should add
>> arc-linux-gnuhf
>> arceb-linux-gnuhf
>>
>> BTW I have oce question: where does one select what default toggles to
>> build the entire software stack with (say -mcpu etc). Does this rely
>> on toolchain driver default to DRTH. One of my problems with
>> rebootstrap was gcc driver defaulting to our legacy cpu. I've cured it
>> there (and planning to upstream the gcc driver patch).
> So here's the lay of the land, apologies for the long email, and if
> some/most of below is not directly relevant to dpkg bug, but I'll
> provide the background so we are all on same page.
>
> We've had 3 revisions of the ISA and ensuing multiple processors in last
> 15 years:
>
> ISA Implementations/Processors (Linux capable)
> ------ ---------------------------------------------------------------
> ARCompact ARC700
> ARCv2 HS38x/HS48x
> ARCv3:32-bit HS58MP
> ARCv3:64-bit HS68MP
>
> - ARCompact is legacy and no new development needed including debian port.
> - Code for one ISA is not compatible with priors, mainly due to addition
> of new instructions. In fact given the configurability of the ISA itself
> (for better or worse), one could end up 2 non-compatible variants of
> same ISA (think double load/store instructions in ARCv2). But the port
> can assume the all encompassing super-set of the ISA as baseline.
> - ARCv3 is currently under development / pre-production but should be
> kept in mind as it is knocking on the door already.
>
> In terms of the ABI critical flavors: there's little/big endian and
> soft/hard-float.
> - Again big endian debian is not needed - mainly because of number of
> customer engagements and resourcing needed to support it
> - ARCv2 hard-float ABI is same as soft - FPU shares the same register
> file so the calling conventions are same. However the triplet is
> different arc-linux-gnuhf [1] as libraries for hard won't run on a
> soft-float system due to lack of emulation etc.
> - ARCv3 does have a dedicated FP register file so there's soft and hard ABIs
>
> So given all of this, I'd like to propose ARCv2 port with hard-float as
> baseline. We don't bother with Big-endian. A soft-float would be
> desirable for debugging and fall-back but not necessary from feature pov.
>
> I'm open to port names as maintainers feel appropriate - but stick with
> current triplets arc-gnu-linux / arc-gnu-linuxhf for ARCv2.
> For ARCv3, we could have arc64* / arc32*
>
> Please let me know if this makes sense.
>
> Once we agree, we can start off with requesting changes to GNU config
> project.
Further to my msg on IRC, we've gotten pretty far along with ARC
rebootstrap [1]. It seems to build 151 packages before failing for perl
and I see similar outcome for riscv64 (which is weird as perl should be
supported there.
Anyhow this is just a polite ping to make some progress on ARC.
Thx,
-Vineet
[1] https://salsa.debian.org/vineetgarc/rebootstrap
_______________________________________________
linux-snps-arc mailing list
linux-snps-arc@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-snps-arc
next prev parent reply other threads:[~2021-05-25 2:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <161152061283.11410.4872085138884291562.reportbug@abrodkin-5550.internal.synopsys.com>
2021-02-06 19:25 ` dpkg: Please add ARC architecture Alexey Brodkin
2021-03-03 18:04 ` Bug#980963: " Helmut Grohne
2021-03-03 18:55 ` Vineet Gupta
2021-03-03 19:35 ` Alexey Brodkin
2021-03-03 19:54 ` Helmut Grohne
2021-03-04 13:55 ` Guillem Jover
2021-03-04 23:56 ` Vineet Gupta
2021-03-26 17:39 ` Vineet Gupta
2021-05-24 20:41 ` Vineet Gupta [this message]
2021-05-28 3:50 ` Guillem Jover
2021-06-02 20:05 ` Vineet Gupta
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=4e8dbf4f-5e91-778f-7139-19a13e49ae4a@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=980963@bugs.debian.org \
--cc=Alexey.Brodkin@synopsys.com \
--cc=Claudiu.Zissulescu@synopsys.com \
--cc=debian-cross@lists.debian.org \
--cc=guillem@debian.org \
--cc=helmut@subdivi.de \
--cc=linux-snps-arc@lists.infradead.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 NNTP newsgroup(s).