This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Shared Code Changes for the RISC-V Glibc Port
- From: Joseph Myers <joseph at codesourcery dot com>
- To: Palmer Dabbelt <palmer at dabbelt dot com>
- Cc: <libc-alpha at sourceware dot org>, <schwab at linux-m68k dot org>, <patches at groups dot riscv dot org>
- Date: Tue, 9 Jan 2018 16:11:17 +0000
- Subject: Re: Shared Code Changes for the RISC-V Glibc Port
- Authentication-results: sourceware.org; auth=none
- References: <20180106073231.20491-1-palmer@dabbelt.com>
On Fri, 5 Jan 2018, Palmer Dabbelt wrote:
> I've run these through build-many-glibcs.py, and while they're not 100% clean I
> think the failures are just problems in my build environment. I'm getting two
I should reiterate that the vast bulk of changes do not need a full
build-many-glibcs.py run. Just because something is changing
system-independent code does not make it require such a run - such a run
rather tends to be indicated if it's changing code in a way that looks
likely to have system-specific issues (and even in that case, a few
particular configurations may be sufficient to test).
Of course each version of the RISC-V port submission should be verified to
pass build-many-glibcs.py *for RISC-V configurations added to
build-many-glibcs.py* (given suitable kernel sources used), but you can
name particular configurations to test on the build-many-glibcs.py command
line rather than testing the full set.
--
Joseph S. Myers
joseph@codesourcery.com