public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Diego Novillo <dnovillo@google.com>
To: gcc <gcc@gcc.gnu.org>
Subject: RFH - Testing targets for the switch to C++
Date: Fri, 06 Apr 2012 22:55:00 -0000	[thread overview]
Message-ID: <CAD_=9DRrko1uYG1t29i+D+=THwdVU5nSqnBvpP5X=CjrACifHQ@mail.gmail.com> (raw)

I have started testing the switch to C++ and there is a pile of
testing to be done.  The testing itself is trivial, but the number of
targets that need to be tested is large and I don't have access to all
these combinations.

My proposal is to make sure that C++ builds work with:

- Primary targets
- Secondary targets
- Any other targets that people regularly test.

The first two items are easy to define.  I took them from
http://gcc.gnu.org/gcc-4.8/criteria.html.

The third item I populated from gcc-testresults postings in 2011.
This gave me a list of 136 targets.  Further, I sorted them by the
number of test reports sent, to determine an idea of "popularity".  I
removed from the list all the targets that had a popularity index
lower than 0.01%.

This is still a large list (about 109 entries), but there are several
overlapping entries (like different flavours of the same basic
target), so it should not be too bad.

The testing plan is, then, to go through this table to make sure that
we can build all of them with C++ enabled for all stages.

I have created a wiki page to track testing progress:
http://gcc.gnu.org/wiki/CppBuildStatus

My plea for help is to everyone who has access to the targets
mentioned in the list: please follow the instructions in that page and
fill-in the table entries of the targets that you tested.

If you see a missing target that should be tested, by all means, add
it to the list.


Thanks.  Diego.

             reply	other threads:[~2012-04-06 22:55 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-06 22:55 Diego Novillo [this message]
2012-04-07 17:16 ` Marc Glisse
2012-04-07 19:01   ` Diego Novillo
2012-04-10  0:26 ` Gerald Pfeifer
2012-04-10 12:37   ` Diego Novillo
2012-04-10 13:05 ` NightStrike
2012-04-10 13:08   ` Diego Novillo
2012-04-10 13:27     ` NightStrike
2012-04-10 13:49       ` Diego Novillo
2012-06-15 16:43     ` NightStrike
2012-06-15 17:24       ` Diego Novillo
2012-06-15 17:41         ` NightStrike
2012-04-10 13:59 ` Paul_Koning
2012-04-10 15:30   ` Diego Novillo
2012-04-10 18:48   ` David Weatherford
2012-04-11 23:51     ` Diego Novillo
2012-04-10 14:36 ` Rainer Orth
2012-04-10 15:30   ` Diego Novillo
2012-04-10 15:33     ` Rainer Orth
2012-04-10 15:53       ` Marc Glisse
2012-04-10 15:58         ` Rainer Orth
2012-04-10 16:14           ` Marc Glisse
2012-04-10 16:22             ` Rainer Orth
2012-04-10 16:28               ` Marc Glisse
2012-04-10 16:38                 ` Diego Novillo
2012-04-11 15:19     ` Rainer Orth
2012-04-11 15:31       ` Diego Novillo
2012-04-12  7:12 ` Sebastian Huber
2012-04-12 12:32   ` Diego Novillo
2012-04-12 15:37     ` Ralf Corsepius
2012-04-12 17:13       ` Diego Novillo
2012-06-06 22:59 ` Thomas Schwinge
2012-06-11 13:48   ` Diego Novillo
2012-06-11 15:03     ` Thomas Schwinge
2012-04-07 20:09 Joel Sherrill
2012-04-07 20:22 ` Diego Novillo

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='CAD_=9DRrko1uYG1t29i+D+=THwdVU5nSqnBvpP5X=CjrACifHQ@mail.gmail.com' \
    --to=dnovillo@google.com \
    --cc=gcc@gcc.gnu.org \
    /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).