From: Joseph Myers <joseph@codesourcery.com>
To: Mikhail Maltsev <maltsevm@gmail.com>
Cc: Jeff Law <law@redhat.com>, <richard.sandiford@arm.com>,
gcc-patches <gcc-patches@gnu.org>
Subject: Re: [PATCH, RFC]: Next stage1, refactoring: propagating rtx subclasses
Date: Mon, 11 May 2015 21:21:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.10.1505112119500.1960@digraph.polyomino.org.uk> (raw)
In-Reply-To: <555113DE.1080201@gmail.com>
On Mon, 11 May 2015, Mikhail Maltsev wrote:
> In general, is there a recommended set of targets that cover most
> conditionally compiled code? Also, the GCC Wiki mentions some automated
See contrib/config-list.mk (note that some of those targets may have
pre-existing build failures, and note that you need to start with a
current trunk native compiler so that --enable-werror-always works; don't
try to build all those cross compilers using an older GCC).
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2015-05-11 21:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 4:38 Mikhail Maltsev
2015-03-31 15:52 ` Trevor Saunders
2015-04-02 21:13 ` Jeff Law
2015-04-25 11:49 ` Richard Sandiford
2015-04-27 16:38 ` Jeff Law
2015-04-27 16:57 ` Richard Sandiford
2015-04-27 20:01 ` Mikhail Maltsev
2015-04-28 13:50 ` Richard Sandiford
2015-04-28 17:12 ` Jeff Law
2015-04-29 8:02 ` Mikhail Maltsev
2015-04-30 3:54 ` Jeff Law
2015-04-30 5:46 ` Jeff Law
2015-05-04 20:32 ` Mikhail Maltsev
2015-05-04 21:22 ` Trevor Saunders
2015-05-09 5:49 ` Trevor Saunders
[not found] ` <5547D40F.6010802@gmail.com>
2015-05-08 21:54 ` Jeff Law
2015-05-11 20:41 ` Mikhail Maltsev
2015-05-11 21:21 ` Joseph Myers [this message]
2015-05-12 20:26 ` Jeff Law
2015-06-06 5:51 ` Mikhail Maltsev
2015-04-28 23:55 ` Jeff Law
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=alpine.DEB.2.10.1505112119500.1960@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gnu.org \
--cc=law@redhat.com \
--cc=maltsevm@gmail.com \
--cc=richard.sandiford@arm.com \
/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).