From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16969 invoked by alias); 1 Nov 2016 22:59:03 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 16923 invoked by uid 89); 1 Nov 2016 22:59:02 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS,URIBL_RED autolearn=ham version=3.3.2 spammy=watching, continuously X-HELO: relay1.mentorg.com Date: Tue, 01 Nov 2016 22:59:00 -0000 From: Joseph Myers To: Carlos O'Donell CC: David Miller , , , Subject: Re: [PATCH v4] Fix -Os related build and test failures. In-Reply-To: <523b1244-6144-ede6-6c94-6515fd093ea6@redhat.com> Message-ID: References: <428b3741-9228-68f3-76ec-d042e4075ded@redhat.com> <54572ad0-f92b-14d2-5238-428978285750@redhat.com> <20161031.085559.1939678123281578460.davem@davemloft.net> <523b1244-6144-ede6-6c94-6515fd093ea6@redhat.com> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-ClientProxiedBy: svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) To svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) X-SW-Source: 2016-11/txt/msg00050.txt.bz2 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 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