From: Mantas Mikaitis <Mantas.Mikaitis@arm.com>
To: gcc-patches@gcc.gnu.org
Subject: Ping: [PATCH][ARM][testsuite] Fix FAIL: gcc.target/arm/macro_defs0.c and macro_defs1.c when -marm forced
Date: Fri, 10 Jul 2015 11:32:00 -0000 [thread overview]
Message-ID: <559FAD4D.10200@arm.com> (raw)
In-Reply-To: <54F82C7E.3050603@arm.com>
Pinging this patch.
Thank you,
- Mantas
On 05/03/15 10:14, Mantas Mikaitis wrote:
> Hello,
>
> Tests gcc.target/arm/macro_defs0.c and gcc.target/arm/macro_defs1.c fail
> in multilib which forces -marm as pointed out in this message:
> https://gcc.gnu.org/ml/gcc-patches/2015-02/msg00483.html .
>
> This patch will cause these tests to be classified as unsupported rather
> than FAIL.
>
> Ok for trunk?
>
> Kind regards,
> Mantas M.
>
> 2015-03-05 Mantas Mikaitis <mantas.mikaitis@arm.com>
>
> * gcc.target/arm/macro_defs0.c: added directive to skip
> test if -marm is present.
> * gcc.target/arm/macro_defs1.c: added directive to skip
> test if -marm is present.
next prev parent reply other threads:[~2015-07-10 11:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 10:14 Mantas Mikaitis
2015-07-10 11:32 ` Mantas Mikaitis [this message]
2015-07-13 16:01 ` Kyrill Tkachov
2015-07-21 9:57 ` Kyrill Tkachov
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=559FAD4D.10200@arm.com \
--to=mantas.mikaitis@arm.com \
--cc=gcc-patches@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).