All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] toolchain: Add glibc support for ARCv2
Date: Thu, 5 Oct 2017 21:30:24 +0000	[thread overview]
Message-ID: <1507239024.31627.18.camel@synopsys.com> (raw)
In-Reply-To: <e199b1b7-2c6f-4711-938a-15616d6d85a1@mind.be>

Hi Arnout,

On Wed, 2017-10-04 at 18:41 +0200, Arnout Vandecappelle wrote:
> 
> On 28-09-17 20:50, Alexey Brodkin wrote:
> > 
> > Hi Thomas, Arnout,
> > 
> > On Fri, 2017-09-15 at 01:14 +0300, Alexey Brodkin wrote:
> > > 
> > > Finally there's working ARC port of glibc thanks to Vineet and Cuper!
> > > This port is based on pretty recent glibc's master branch and ARC
> > > changes are being reviewed now in glibc's mailing list.
> > > 
> > > Thus we again have to use sources from our GitHub but as soon as there's
> > > a glibc release with our patches applied we'll switch to unpstream releases
> > > and will drop our glibc GitHub repo alltogether.
> > > 
> > > Note now we cut tags in glibc repo simultaneously with tags
> > > in Binutils and GCC repos and so to make sure everything works in the best
> > > way we plan to update glibc tag together with Binutils and GCC.
> > > 
> > > Also note as of today ARCompact (AKA ARCv1 ISA) is not supported in glibc
> > > but we plan to fix it soonish so for now we make glibc intentionally
> > > dependent on archs38.
> > > 
> > > Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
> > > Cc: Cupertino Miranda <cmiranda@synopsys.com>
> > > Cc: Vineet Gupta <vgupta@synopsys.com>
> > > Cc: Anton Kolesov <akolesov@synopsys.com>
> > 
> > This patch was sitting in patchwork for 2 weeks now.
> > If there're any complaints an suggestions why don't we merge it?
> 
> ?Since I merged the bump to glibc 2.26, patch 1 is not correct anymore.

I'll send a respin shortly, OK?

> ?Would it be useful to instead add patches to our glibc to add ARC support? Or
> are the ARC patches too difficult to backport?

Well not now definitely. The point is:
?a) ARC port is not yet merged upstream
?b) Our patches are on top of pretty much up-to-date master branch,
? ? which means they alone won't apply on top of the most recent release

> 
> 
> > 
> > I'd like to see how we ramp-up with glibc toolchain for ARC.
> > That said once the patch is applied would be good to add
> > a corresponding config for autobuilder.
> 
> ?You can actually do that yourself by adding a config to
> support/config-fragments/autobuild and updating toolchain-configs.csv
> in that directory. Something like br-arc-full-internal.config but then with glibc.

Sure, will do once glibc for ARC is supported in BR.

-Alexey

      reply	other threads:[~2017-10-05 21:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-14 22:14 [Buildroot] [PATCH 0/2] toolchain: Add glibc support for ARCv2 Alexey Brodkin
2017-09-14 22:14 ` [Buildroot] [PATCH 1/2] glibc: Move patches to version-specific folder Alexey Brodkin
2017-09-14 22:14 ` [Buildroot] [PATCH 2/2] toolchain: Add glibc support for ARCv2 Alexey Brodkin
2017-09-28 18:50   ` Alexey Brodkin
2017-10-04 16:41     ` Arnout Vandecappelle
2017-10-05 21:30       ` Alexey Brodkin [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=1507239024.31627.18.camel@synopsys.com \
    --to=alexey.brodkin@synopsys.com \
    --cc=buildroot@busybox.net \
    /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.