ARC Moving to @pcl relocations
A message that is not in the archive (sent off-list or not yet received): [email protected]
cover ARC Moving to @pcl relocations
Hi Andrew,
Quoted 14 lines · Andrew Burgess
This is a slightly odd series of 2 patches. The two patches are actually alternative solutions to the same problem. I'm keen to see one of these merged, but I don't know which method would be preferred.
This commit aims to address an issue that was introduced / mentioned in commit
20554a78a9bba278c6b9cbbb4cfc5bde3772c56d(ARC:
Conditionalise certain relocations as provided by TLS tools only).The problem is that not all historic versions of binutils have supported the @pcl relocation type. This problem is compounded by the fact that the arithmetic construct that was previously used to synthesise an @pcl like behaviour, does not work on recent versions of binutils.
Quoted 4 lines
In the commit
20554a78acode was added that selects between the new style @pcl relocations, and the old style arithmetic construct, however, this selection is done based on whether the uClibc user has configured with native threads or not.
Right - the idea at the time was @pcl was added to tools for TLS/NPTL support and thus uClibc NPTL loosely implied that your tools will have that support - but this was not the ideal choice I agree.
Quoted 9 lines
Of course, a uClibc user could choose to use a modern version of binutils AND configure without native thread support, in which case uClibc will not compile.
I have two proposed solutions. In patch 1/2 I simply drop support for the older versions of binutils in favour of the new @pcl relocation type. This feels the cleanest solution, but I don't know how strongly the uClibc(-ng) community feels about maintaining compatibility for older versions of the tools.
So this was reported recently by Waldemar's build service too.
http://mailman.uclibc-ng.org/pipermail/devel/2016-July/001072.html
And we have an exact same patch floated internally which Vlad sent out earlier this week
Quoted 2 lines
Given that I anticipated push back against the first patch I took a look at how I might maintain compatibility.
Not really - while indeed 1/2 opens up a non-compatibilty window, there is less likelihood people will mix-n-match different baselines of uclibc and gcc/gas. So Vlad's patch does exactly that.
Quoted 6 lines
It turns out to be pretty
easy, and that is patch 2/2. In this patch I drew inspiration from similar examples in the Rules.mak file to check if the toolchain supports @pcl relocations or not. With this done we have a new define based on the specific toolchain feature being supported or not, which can then be used to conditionalise the code.
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 ?
-Vineet
Quoted 5 lines
Would you consider merging one of these patches?
Thanks,
Andrew
cover ARC Moving to @pcl relocations
Quoted 68 lines · Vineet Gupta
Hi Andrew,
Quoted 3 lines · Andrew Burgess
This is a slightly odd series of 2 patches. The two patches are actually alternative solutions to the same problem. I'm keen to see one of these merged, but I don't know which method would be
preferred.
Quoted 7 lines
This commit aims to address an issue that was introduced / mentioned in commit
20554a78a9bba278c6b9cbbb4cfc5bde3772c56d(ARC:
Conditionalise certain relocations as provided by TLS tools only).The problem is that not all historic versions of binutils have supported the @pcl relocation type. This problem is compounded by
the
Quoted 2 lines
fact that the arithmetic construct that was previously used to synthesise an @pcl like behaviour, does not work on recent versions
of
Quoted 6 lines
binutils.
In the commit
20554a78acode was added that selects between the new style @pcl relocations, and the old style arithmetic construct, however, this selection is done based on whether the uClibc user has configured with native threads or not.Right - the idea at the time was @pcl was added to tools for TLS/NPTL support and
thus uClibc NPTL loosely implied that your tools will have that support
- but this
was not the ideal choice I agree.Quoted 5 lines
Of course, a uClibc user could choose to use a modern version of binutils AND configure without native thread support, in which case uClibc will not compile.
I have two proposed solutions. In patch 1/2 I simply drop support
for
Quoted 2 lines
the older versions of binutils in favour of the new @pcl relocation type. This feels the cleanest solution, but I don't know how
strongly
Quoted 2 lines
the uClibc(-ng) community feels about maintaining compatibility for older versions of the tools.
So this was reported recently by Waldemar's build service too.
http://mailman.uclibc-ng.org/pipermail/devel/2016-July/001072.html
And we have an exact same patch floated internally which Vlad sent out earlier
this weekQuoted 2 lines
Given that I anticipated push back against the first patch I took a look at how I might maintain compatibility.
Not really - while indeed 1/2 opens up a non-compatibilty window, there is less
likelihood people will mix-n-match different baselines of uclibc and gcc/gas. So
Vlad's patch does exactly that.Quoted 4 lines
It turns out to be pretty
easy, and that is patch 2/2. In this patch I drew inspiration from similar examples in the Rules.mak file to check if the toolchain supports @pcl relocations or not. With this done we have a newdefine
Quoted 2 lines
based on the specific toolchain feature being supported or not, which can then be used to conditionalise the code.
Quoted 6 lines
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.
Thanks,
Quoted 7 lines
-Vineet
Quoted 4 lines
Would you consider merging one of these patches?
Thanks,
Andrew
cover ARC Moving to @pcl relocations
Quoted 8 lines · Bernhard Reutner-Fischer
Quoted 6 lines
Indeed your 2/2 seems to be the most "past-proof" code change. So I
Quoted 5 lines
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.
Thx,
-Vineet
cover ARC Moving to @pcl relocations
Hi Andrew, all,
Quoted 9 lines · Vineet Gupta
Quoted 8 lines · Bernhard Reutner-Fischer
Quoted 8 lines
Indeed your 2/2 seems to be the most "past-proof" code change. So I
Quoted 5 lines
would think it
is indeed better and is something I should have done in the first place.
Quoted 7 lines
Quoted 3 lines
Quoted 1 line
Quoted 1 line
@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?
-Alexey
cover ARC Moving to @pcl relocations
Quoted 29 lines · Alexey Brodkin
Hi Andrew, all,
Quoted 9 lines · Vineet Gupta
Quoted 8 lines · Bernhard Reutner-Fischer
Quoted 8 lines
Indeed your 2/2 seems to be the most "past-proof" code change. So I
Quoted 5 lines
would think it
is indeed better and is something I should have done in the first place.Quoted 7 lines
Quoted 3 lines
Quoted 1 line
Quoted 1 line
@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.
Quoted 6 lines
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
c5187While 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
cover ARC Moving to @pcl relocations
Quoted 38 lines · Andrew Burgess
Quoted 29 lines · Alexey Brodkin
Hi Andrew, all,
Quoted 9 lines · Vineet Gupta
Quoted 8 lines · Bernhard Reutner-Fischer
Quoted 8 lines
Indeed your 2/2 seems to be the most "past-proof" code change. So I
Quoted 5 lines
would think it
is indeed better and is something I should have done in the first place.Quoted 7 lines
Quoted 3 lines
Quoted 1 line
Quoted 1 line
@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.
Quoted 6 lines
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
c5187While Andrew just replaces ".&" construction with "@pcl". I'm wondering which is the correct approach here?
Quoted 7 lines
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).
Having looked at this a little more I think that we should merge the section Alexey mentioned above. In the second instance (the one I modified) we use the symbol _dl_start, while in the first we use _DYNAMIC.
However, the comment in the first block makes it clear the symbol used should be a global symbol, not a local, and _dl_start is a local symbol.
The consequence of using a local here is that we end up with a R_ARC_NONE relocation being generated again the .got.
[ The generation of the R_ARC_NONE is probably a bug, or at least a
lack of optimisation, but it is what happens with the current upstream tools. ]
As the arc dynamic loader does not currently support patching R_ARC_NONE during the bootstrap phase, if uClibc(-ng) is configured without native threads, then currently we get a dynamic loader that does not work.
So, I think we should collapse both sections, and make use of the _DYNAMIC symbol instead of _dl_start. I've included a revised version of patch 1/2 that includes this latest change.
Thanks,
Andrew
----
[PATCH] ARC: Update relocation syntax for old-thread model code
This commit reverses a change introduced in commit 20554a78a9bba that split some of the ARC code into two based on whether uClibc was configured with native threads or not.
The native thread code was updated to use the relocation syntax of modern binutils, while the non-native code path used a syntax only accepted in older versions of binutils.
The problem with this is that the choice of old binutils or not is orthogonal to the choice of native threads or not, and so, inevitably a user with a recent version of binutils can make the choice to configure uClibc with non-native thread support, and run into code that will not assemble.
The solution is either to abandon support for the old tools completely, or to add a new compile time flag for ARC that is set when the version of binutils being used is old; this new flag would allow the old relocation structure to be selected.
In this commit I have simply dropped support for older versions of the tools.
--- ldso/ldso/arc/dl-startup.h | 7 ------- ldso/ldso/arc/dl-sysdep.h | 10 ---------- 2 files changed, 17 deletions(-)
ldso/ldso/arc/dl-startup.h +0 -7
@@ -34,15 +34,8 @@ __asm__(" ; skip the extra args calc by dl_start() \n" " ld_s r1, [sp] ; orig argc from aux-vec Tbl \n" -#ifdef __UCLIBC_HAS_THREADS_NATIVE__" ld r12, [pcl, _dl_skip_args at pcl] \n" -" add r2, pcl, _dl_fini at pcl ; finalizer \n" -#else - " add r12, pcl, _dl_skip_args-.+(.&2) \n" - " ld r12, [r12] \n" - " add r2, pcl, _dl_fini-.+(.&2) ; finalizer \n" -#endif" add2 sp, sp, r12 ; discard argv entries from stack\n" " sub_s r1, r1, r12 ; adjusted argc, on stack \n"
ldso/ldso/arc/dl-sysdep.h +0 -10
@@ -132,7 +132,6 @@ static __always_inline Elf32_Addr elf_machine_dynamic(void)/* Return the run-time load address of the shared object. */ static __always_inline Elf32_Addr elf_machine_load_address(void) { -#ifdef __UCLIBC_HAS_THREADS_NATIVE__/* To find the loadaddr we subtract the runtime addr of a non-local symbol * say _DYNAMIC from it's build-time addr. * N.B., gotpc loads get optimized by the linker if it finds the symbol
@@ -150,15 +149,6 @@ static __always_inline Elf32_Addr elf_machine_load_address(void) "sub %0, %0, %1 ;delta" "\n" : "=&r" (addr), "=r"(tmp) ); -#else -Elf32_Addr addr, tmp; - __asm__ ( -"ld %1, [pcl, _dl_start at gotpc] ;build addr of _dl_start \n" -"add %0, pcl, _dl_start-.+(.&2) ;runtime addr of _dl_start \n" -"sub %0, %0, %1 ;delta \n" - :"=&r" (addr),"=r" (tmp) - ); -#endif return addr; }
Signature · 1 line
2.5.1
cover ARC Moving to @pcl relocations
Hi Andrew,
Andrew Burgess wrote,
Quoted 64 lines · Andrew Burgess
Quoted 39 lines · Alexey Brodkin
Quoted 30 lines
Hi Andrew, all,
Quoted 9 lines · Vineet Gupta
Quoted 8 lines · Bernhard Reutner-Fischer
Quoted 8 lines
Indeed your 2/2 seems to be the most "past-proof" code change. So I
Quoted 5 lines
would think it
is indeed better and is something I should have done in the first place.Quoted 7 lines
Quoted 3 lines
Quoted 1 line
Quoted 1 line
@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.
Quoted 6 lines
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
c5187While Andrew just replaces ".&" construction with "@pcl". I'm wondering which is the correct approach here?
Quoted 7 lines
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).
Having looked at this a little more I think that we should merge the section Alexey mentioned above. In the second instance (the one I modified) we use the symbol
_dl_start, while in the first we use_DYNAMIC.However, the comment in the first block makes it clear the symbol used should be a global symbol, not a local, and
_dl_startis a local symbol.The consequence of using a local here is that we end up with a
R_ARC_NONErelocation being generated again the .got.[ The generation of the
R_ARC_NONEis probably a bug, or at least a
lack of optimisation, but it is what happens with the current upstream tools. ]
Quoted 8 lines
As the arc dynamic loader does not currently support patching
R_ARC_NONEduring the bootstrap phase, if uClibc(-ng) is configured without native threads, then currently we get a dynamic loader that does not work.So, I think we should collapse both sections, and make use of the
_DYNAMICsymbol instead of_dl_start. I've included a revised version of patch 1/2 that includes this latest change.
Thanks, simplification is always good.
Applied and pushed,
Waldemar