From: Diego Novillo <dnovillo@google.com>
To: Joel Sherrill <joel.sherrill@oarcorp.com>
Cc: gcc <gcc@gcc.gnu.org>
Subject: Re: RFH - Testing targets for the switch to C++
Date: Sat, 07 Apr 2012 20:22:00 -0000 [thread overview]
Message-ID: <4F80A1E3.20808@google.com> (raw)
In-Reply-To: <ul0br9va73ygmhlb46bhlkp0.1333829354814@email.android.com>
On 4/7/12 4:09 PM, Joel Sherrill wrote:
> For *-rtems* all test results are cross with tests run on simulators.
> We use a native compiler bulit from the same source for testing.
> Newlib is the C library and built at the same time.
>
> Do we need to enable any special flags from our existing configure?
Just add --enable-build-with-cxx to the configure call. The C++ testing
wiki page has full details.
>
> FWIW we have a few targets where the simulator is limited in memory
> and many tests fail. These get rejected because the mail message is
> too large. If someone is willing to help us trim things so the known
> failures get skipped, it would be appreciated. We would report more.
> :)
Perhaps you could use the script
contrib/testsuite-management/validate_failures.py? You can add those
tests that are known to fail to a manifest file. It will then only
report the failures that are not in that manifest.
The only thing with this script is that it is not used by default by
make check nor the testsuite reporting script. You'd have to call it
from there.
Thanks. Diego.
next prev parent reply other threads:[~2012-04-07 20:22 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-07 20:09 Joel Sherrill
2012-04-07 20:22 ` Diego Novillo [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-04-06 22:55 Diego Novillo
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
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=4F80A1E3.20808@google.com \
--to=dnovillo@google.com \
--cc=gcc@gcc.gnu.org \
--cc=joel.sherrill@oarcorp.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).