This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH v4] Fix -Os related build and test failures.
- From: Joseph Myers <joseph at codesourcery dot com>
- To: Carlos O'Donell <carlos at redhat dot com>
- Cc: David Miller <davem at davemloft dot net>, <schwab at suse dot de>, <fweimer at redhat dot com>, <libc-alpha at sourceware dot org>
- Date: Tue, 1 Nov 2016 22:58:42 +0000
- Subject: Re: [PATCH v4] Fix -Os related build and test failures.
- Authentication-results: sourceware.org; auth=none
- References: <428b3741-9228-68f3-76ec-d042e4075ded@redhat.com> <mvmins8hq95.fsf@hawking.suse.de> <54572ad0-f92b-14d2-5238-428978285750@redhat.com> <20161031.085559.1939678123281578460.davem@davemloft.net> <523b1244-6144-ede6-6c94-6515fd093ea6@redhat.com>
On Mon, 31 Oct 2016, Carlos O'Donell wrote:
> I'm going to setup a non-x86_64 cross-build to test this.
> I think I can do it easily enough on Fedora so I can keep
> it up to date for upstream builds.
FYI: I'm writing a script to run glibc builds (and the part of the tests
that don't involve running host code), including building the cross
compilers, for lots of configurations (a rough sort of equivalent to GCC's
contrib/config-list.mk). I think such a script would be useful to have in
glibc, though it would take to long to use for testing most patches (it
should aim to cover all ABI variants in
<https://sourceware.org/glibc/wiki/ABIList> and enough other variants e.g.
for CPUs using different sysdeps directories to test building each piece
of code in glibc at least once) - but it might be useful to have a bot
running it continuously and watching for regressions.
--
Joseph S. Myers
joseph@codesourcery.com