public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Christian Bruel <christian.bruel@st.com>
To: Kyrill Tkachov <kyrylo.tkachov@arm.com>,
	       "msebor@redhat.com"	<msebor@redhat.com>,
	       "ramana.radhakrishnan@foss.arm.com"
	<ramana.radhakrishnan@foss.arm.com>,
	       "gcc-patches@gcc.gnu.org"	<gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH testsuite, ARM] skip Wno-frame-address tests
Date: Thu, 20 Aug 2015 14:57:00 -0000	[thread overview]
Message-ID: <55D5E293.9070003@st.com> (raw)
In-Reply-To: <55D5DAC9.6070001@arm.com>



On 08/20/2015 03:48 PM, Kyrill Tkachov wrote:
> Hi Christian,
>
> On 20/08/15 14:45, Christian Bruel wrote:
>> Hello,
>>
>> 2 tests from rev 226480 introduced a new failure for ARM testing -Werror
>> because a warning is always emitted regardless -Wframe-address is given
>> or not.
>>
>>    From expand_builtin_frame_address:
>>
>>     /* Some ports cannot access arbitrary stack frames.  */
>>          if (tem == NULL)
>> 	{
>> 	  warning (0, "unsupported argument to %qD", fndecl);
>> 	  return const0_rtx;
>> 	}
>>
>> This patch just skips the test on ARM that can't access arbitrary stack
>> frame anyway and will always warn.
>>
>> OK for trunk ? thanks,
>>
>> Christian
>>
>>
>>
>>
>>
>> 	
>>
>> no-frame-address.patch
>>
>>
>> 015-08-20  Christian Bruel<christian.bruel@st.com>
>>
>> 	* gcc.dg/Wno-frame-address.c: Skip for ARM.
>> 	* g++.dg/Wno-frame-address.C: Ditto.
>>
>> Index: gcc/testsuite/gcc.dg/Wno-frame-address.c
>> ===================================================================
>> --- gcc/testsuite/gcc.dg/Wno-frame-address.c	(revision 227030)
>> +++ gcc/testsuite/gcc.dg/Wno-frame-address.c	(working copy)
>> @@ -1,4 +1,5 @@
>>    /* { dg-do compile } */
>> +/* { dg-skip-if "Cannot access arbitrary stack frames. " { arm*-*-* } { "*" } { "" } } */
>>    /* { dg-options "-Werror" } */
>>
>>    /* Verify that -Wframe-address is not enabled by default by enabling
>> Index: gcc/testsuite/g++.dg/Wno-frame-address.C
>> ===================================================================
>> --- gcc/testsuite/g++.dg/Wno-frame-address.C	(revision 227030)
>> +++ gcc/testsuite/g++.dg/Wno-frame-address.C	(working copy)
>> @@ -1,4 +1,5 @@
>>    // { dg-do compile }
>> +/* { dg-skip-if "Cannot access arbitrary stack frames. " { arm*-*-* } { "*" } { "" } } */
>>    // { dg-options "-Werror" }
>
> Use the C++-style comment here.

oops yes. cut and pasted.

> Otherwise looks ok to me, though if more tests like this crop we'd want a
> dg-requires-effective-target check that filters out the targets that don't
> implement this feature.

agree, if more targets come up with the same failure a predicate helper 
will be useful.

thanks

Christian


>
> Kyrill
>
>>
>>    // Verify that -Wframe-address is not enabled by default by enabling
>

  parent reply	other threads:[~2015-08-20 14:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-20 13:49 Christian Bruel
2015-08-20 13:53 ` Kyrill Tkachov
2015-08-20 14:05   ` Rainer Orth
2015-08-20 14:57   ` Christian Bruel [this message]
2015-08-20 16:39 ` 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=55D5E293.9070003@st.com \
    --to=christian.bruel@st.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=kyrylo.tkachov@arm.com \
    --cc=msebor@redhat.com \
    --cc=ramana.radhakrishnan@foss.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).