From: Carlos O'Donell <carlos@redhat.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: David Miller <davem@davemloft.net>,
schwab@suse.de, fweimer@redhat.com, libc-alpha@sourceware.org
Subject: Re: [PATCH v4] Fix -Os related build and test failures.
Date: Wed, 02 Nov 2016 12:52:00 -0000 [thread overview]
Message-ID: <23a47c57-6aee-5824-1445-ed8943d7b279@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1611012255140.10022@digraph.polyomino.org.uk>
On 11/01/2016 06:58 PM, Joseph Myers wrote:
> 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.
That would be excellent. Please publish the script so that others can use it.
I have a similar script, but not yet setup for cross-compiles.
Cheers,
Carlos.
next prev parent reply other threads:[~2016-11-02 12:52 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-28 4:48 [PATCH] Fix -Os related -Werror failures Carlos O'Donell
2016-10-28 6:25 ` Andreas Schwab
2016-10-28 6:32 ` Florian Weimer
2016-10-28 6:44 ` Jeff Law
2016-10-28 8:12 ` Arnd Bergmann
2016-10-28 8:17 ` Andrew Pinski
2016-10-28 13:28 ` Jeff Law
2016-10-28 20:10 ` Paul Eggert
2016-10-29 3:03 ` Jeff Law
2016-10-30 4:25 ` Paul Eggert
2016-10-28 12:09 ` Carlos O'Donell
2016-10-28 12:43 ` Florian Weimer
2016-10-28 13:04 ` Joseph Myers
2016-10-28 13:07 ` Carlos O'Donell
2016-10-28 12:49 ` Joseph Myers
2016-10-28 12:55 ` Florian Weimer
2016-10-28 13:18 ` Carlos O'Donell
2016-10-28 13:58 ` [PATCH v2] Fix -Os related build and test failures Carlos O'Donell
2016-10-28 14:17 ` Joseph Myers
2016-10-29 2:59 ` [PATCH v3] " Carlos O'Donell
2016-10-29 3:26 ` Carlos O'Donell
2016-10-29 17:35 ` Joseph Myers
2016-10-30 3:51 ` [PATCH v4] " Carlos O'Donell
2016-10-31 8:33 ` Andreas Schwab
2016-10-31 9:16 ` Carlos O'Donell
2016-10-31 9:22 ` Florian Weimer
2016-10-31 12:56 ` David Miller
2016-10-31 19:56 ` Carlos O'Donell
2016-11-01 22:59 ` Joseph Myers
2016-11-02 12:52 ` Carlos O'Donell [this message]
2016-11-01 9:17 ` Andreas Schwab
2016-11-01 11:13 ` Joseph Myers
2016-11-01 15:58 ` Tamar Christina
2016-11-01 16:06 ` David Miller
2016-11-01 16:15 ` Tamar Christina
2016-11-02 11:53 ` Carlos O'Donell
2016-11-02 17:03 ` Carlos O'Donell
2016-11-02 13:22 ` Carlos O'Donell
2016-10-31 18:38 ` [PATCH v3] " Steve Ellcey
2016-10-31 19:50 ` Carlos O'Donell
2016-10-31 19:57 ` Steve Ellcey
2016-10-31 20:50 ` Carlos O'Donell
2016-10-31 21:00 ` Steve Ellcey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=23a47c57-6aee-5824-1445-ed8943d7b279@redhat.com \
--to=carlos@redhat.com \
--cc=davem@davemloft.net \
--cc=fweimer@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=schwab@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).