From: andrew.burgess@embecosm.com (Andrew Burgess)
To: linux-snps-arc@lists.infradead.org
Subject: [PATCH 0/2] ARC Moving to @pcl relocations
Date: Fri, 29 Jul 2016 10:43:17 +0100 [thread overview]
Message-ID: <20160729094317.GM4517@embecosm.com> (raw)
In-Reply-To: <1469782070.3088.10.camel@synopsys.com>
* Alexey Brodkin <Alexey.Brodkin at synopsys.com> [2016-07-29 08:49:22 +0000]:
> Hi Andrew, all,
>
> On Thu, 2016-07-28@15:40 -0700, Vineet Gupta wrote:
> > On 07/28/2016 03:04 PM, Bernhard Reutner-Fischer wrote:
> > >
> > > >
> > > > Indeed your 2/2 seems to be the most "past-proof" code change. So I
> > > > >
> > > > > would think it
> > > > > is indeed better and is something I should have done in the first
> > > > > place.
> > > > >
> > > > > @Alexey, @Vlad what say you ?
> > > uClibc traditionally supports the current stable release of binutils, which would make it patch #1 I think.
> > >
> >
> > But 2/2 works for both and makes actual binutils version moot. FWIW, ARC tools
> > don't as of last release didn't use the upstream/stable binutils, but we are
> > pretty close to that now though.
>
> Personally I'd prefer to not add more conditional defines in uClibc but
> make it a little-bit simpler.
>
> I.e. either Vlad's patch or #1 from this series IMHO looks better.
> It's been quite some time since we updated our tools with PCL support
> and I'm not really sure if there's anybody interested in using ages old
> tools with today's uClibc. We don't test such combinations and there could
> be issues already in such combos.
>
> BTW I noticed that Vlad's patch removes/reverts that thing as well:
> http://cgit.uclibc-ng.org/cgi/cgit/uclibc-ng.git/commit/ldso/ldso/arc/dl-sysdep.h?id=181d410ad00cddd1d6c9f4835e129136b74
> c5187
>
> While Andrew just replaces ".&" construction with "@pcl".
> I'm wondering which is the correct approach here?
I left the second block in as the two blocks use different symbols,
the native threads block uses _DYNAMIC, while the non-native uses
_dl_start.
I wasn't sure if this was significant, so left the the split in
place. If more knowledgeable folk believe these can be combined then
that's fine with me (so long as we combine on @pcl).
Thanks,
Andrew
next prev parent reply other threads:[~2016-07-29 9:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1469729044.git.andrew.burgess@embecosm.com>
2016-07-28 18:50 ` [PATCH 0/2] ARC Moving to @pcl relocations Vineet Gupta
2016-07-28 22:04 ` Bernhard Reutner-Fischer
2016-07-28 22:40 ` Vineet Gupta
2016-07-29 8:49 ` Alexey Brodkin
2016-07-29 9:43 ` Andrew Burgess [this message]
2016-07-29 13:26 ` Andrew Burgess
2016-07-31 10:56 ` [uclibc-ng-devel] " Waldemar Brodkorb
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=20160729094317.GM4517@embecosm.com \
--to=andrew.burgess@embecosm.com \
--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.