From: Jonathan Wakely <jwakely@redhat.com>
To: Szabolcs Nagy <szabolcs.nagy@arm.com>
Cc: "libstdc++@gcc.gnu.org" <libstdc++@gcc.gnu.org>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] mark libstdc++ tests unsupported if they fail with "relocation truncated"
Date: Thu, 15 Oct 2015 10:15:00 -0000 [thread overview]
Message-ID: <20151015101525.GD12094@redhat.com> (raw)
In-Reply-To: <561CCAF0.8010200@arm.com>
On 13/10/15 10:12 +0100, Szabolcs Nagy wrote:
>Dejagnu tweak:
>Check the compiler output in libstdc++-dg-test using
>${tool}_check_unsupported_p and mark the output
>unsupported accordingly to avoid "relocation truncated"
>failures cluttering the test results on aarch64-none-elf
>with -mcmodel=tiny. (gcc torture tests already use this
>predicate for this reason.)
>
>This is a revision of
>https://gcc.gnu.org/ml/libstdc++/2015-01/msg00198.html
>which had problems because the unsupported result was
>propagated to and handled by dg-runtest differently
>than expected.
>
>Is it OK?
OK, assuming this was tested on a primary platform and didn't change
the libstdc++ testresults.
prev parent reply other threads:[~2015-10-15 10:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 9:12 Szabolcs Nagy
2015-10-15 10:15 ` Jonathan Wakely [this message]
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=20151015101525.GD12094@redhat.com \
--to=jwakely@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.org \
--cc=szabolcs.nagy@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).