All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Guillem Jover <guillem@debian.org>,
	Vineet Gupta <Vineet.Gupta1@synopsys.com>,
	"980963@bugs.debian.org" <980963@bugs.debian.org>,
	Alexey Brodkin <Alexey.Brodkin@synopsys.com>,
	"linux-snps-arc@lists.infradead.org"
	<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: Wed, 2 Jun 2021 20:05:17 +0000	[thread overview]
Message-ID: <17c67381-c7a6-1917-b53f-c8fe89600f8b@synopsys.com> (raw)
In-Reply-To: <YLBodXkvCmMgO+ia@thunder.hadrons.org>

Hi Guillem,

On 5/27/21 8:50 PM, Guillem Jover wrote:
> I discussed this today with Vineet on IRC in #debian-bootstrap, to try
> to clarify some things, and this is the summary I think:
>
> * ARCv2 32-bit little-endian
>
>    - The arch based on ARCv2 32-bit is going to be little-endian, and
>      ideally will be hard-float, but that's pending on a patch for gcc,
>      to flip the default from soft-float. From what I understand while
>      hard and soft-float are ABI compatible in the ISA and calling
>      convention sense, they are not ABI compatible in the object
>      linking sense, and while I guess this could also perhaps be lifted,
>      it's not currently the case. My concern is that adding the support
>      before the default has been switched might mean "ABI incompatible"
>      architectures if we cannot link objects. Vineet, mentioned that
>      they might be fine settling with soft-float in that case, even
>      with the performance penalty implied (in that case, personally I
>      think adding the -gnuhf triplet would be better, but I'd not be
>      going to be doing the work, so… :). The patch is supposed to be
>      sent upstream around next week or so. I'd prefer to wait what
>      ends up happening there, TBH, before committing the support to
>      dpkg. As I've mentioned I'm fine with committing it once it hits
>      upstream git though.
>    - The triplet would be «arc-linux-gnu», the Debian architecture
>      would be «arc».

FWIW gcc patch is now in mainline (I've requested Claudiu for backport)

2021-06-02 46d04271a498 ARC: gcc driver default to hs38_linux

Thx,
-Vineet

_______________________________________________
linux-snps-arc mailing list
linux-snps-arc@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-snps-arc

      reply	other threads:[~2021-06-02 20:05 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
2021-05-28  3:50         ` Guillem Jover
2021-06-02 20:05           ` Vineet Gupta [this message]

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=17c67381-c7a6-1917-b53f-c8fe89600f8b@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.