[uclibc-ng-devel] [PATCH] ldso/ARC: fix DT_RELACOUNT handling

Alexey Brodkin Alexey.Brodkin at synopsys.com
Tue May 31 15:58:36 UTC 2016


Hi Waldemar,

On Tue, 2016-05-31 at 06:15 +0200, Waldemar Brodkorb wrote:
> Hi,
> Waldemar Brodkorb wrote,
> 
> > 
> > Hi,
> > Waldemar Brodkorb wrote,
> > 
> > > 
> > > Hi Vineet,
> > > Vineet Gupta wrote,
> > > 
> > > > 
> > > > On Sunday 29 May 2016 01:30 AM, Waldemar Brodkorb wrote:
> > > > > 
> > > > > ARC has between 28-30 failures even with latest binutils/gcc
> > > > Latest here is pretty overloaded :-) We had 2016.03 release recently and then
> > > > there's bleeding edge binutils atleast which is tracking pretty close to upstream
> > > > binutils.
> > > > 
> > > > What exact versions of these tools are you using.
> > > I am using 2016.03. I wanted to say latest release :=)
> > > 
> > > The 1.0.15 testrun is not yet finished, but I think it is
> > > simply reproducable by running nsim and uclibcng-testrunner.sh.
> > Nsim is nice to script, but the performance
> > is pretty bad. Running the testsuite takes for the four combinations
> > (arc700,archs,little and big mode) mostly the same time as 
> > running all the other tests in Qemu :)
> > 1 CORE 100 % CPU...
> > 
> > Would be NSIM Pro faster?
> Here are the 1.0.15 results:
> http://tests.embedded-test.org/uClibc-ng/1.0.15/

Thank you so much for doing that, appreciate it a lot!

I'm wondering if there's a reason why did you use Linux 4.4
instead of latest (4.6)? Since we push all out stuff upstream
chances are some failures won't happen with more recent kernel.

Also from the logs it's not clear what tools were used?
Was it latest stable arc-2016.03, previous arc-2015.12?
I'd like to have this information to narrow down investigation of
failure reasons.

-Alexey


More information about the uClibc mailing list