Re: MicroBlaze glibc fixes

[Waldemar Brodkorb <wbx at openadk dot org>]

Hi,
Szabolcs Nagy wrote,

> On 05/01/17 17:11, Joseph Myers wrote:
> > On Thu, 5 Jan 2017, Michael Eager wrote:
> > 
> >> Hi Joseph --
> >>
> >> I don't have a MicroBlaze Linux installation.  I can't comment on
> >> the failures you encountered.
> > 
> > Is there anyone who does have such an installation and can run the full 
> > glibc testsuite (both compilation and execution tests - either native or 
> > cross testing is fine) during the freeze period each release cycle, report 
> > the results on that release's wiki page and hopefully fix any obvious 
> > breakage shown in the results?  If not, we should consider obsoleting the 
> > port.
> > 
> 
> openadk.org has microblaze setup, but i don't know
> if it wants to take on the burden of glibc testing
> and port maintenance.

I actually do some kind of regular glibc testing with embedded-test
and OpenADK infrastructure. For other C libraries I publish the
results: http://tests.embedded-test.org/

The problem I have with glibc runtime testing is that
at the moment it seems that the tests can't be cross-compiled and
then only run on a target or emulator without having either NFS
or SSH working.

In embedded-test I create a Linux kernel and initramfs and bootup
the result in Qemu or other emulators. It is not guaranteed that
I have networking available inside the emulator.

Would it be possible to reorganize the internal testsuite to allow
the separation of compiling and running the tests?

I have done this for my little uClibc spin-off and added a
small shell script which runs the tests and summarize the results.
This can be run with hush on noMMU targets. (GNU make requires
fork()). Furthermore I have split-out the testsuite completely to
be able to compile all tests as regular applications with the full
gcc compiler.
(http://cgit.uclibc-ng.org/cgi/cgit/uclibc-ng-test.git)
The testsuite can be run on glibc systems. 

Would this be enough for you to get some idea about the quality of
the next glibc release? 

I could run 2.24 and latest git to show any regressions or
improvements if there is any interest.
 
> and i know that gcc needs a patch to compile musl
> correctly on microblaze, the patch is pending on
> the gcc bugzilla for almost two years now
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65649

That is only required if your host is 32Bit. So it doesn't prevent
using microbaze for all kind of cross-toolchain users.
 
best regards
 Waldemar