From: Jakub Jelinek <jakub@redhat.com>
To: Jeff Law <law@redhat.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [committed] Fix -fstack-check with really big frames on aarch64
Date: Thu, 22 Jun 2017 17:28:00 -0000 [thread overview]
Message-ID: <20170622172812.GA2123@tucnak> (raw)
In-Reply-To: <f249de4a-5ed4-43df-125f-320c28a9a207@redhat.com>
On Thu, Jun 22, 2017 at 11:21:15AM -0600, Jeff Law wrote:
> +2017-06-22 Jeff Law <law@redhat.com>
> +
> + * gcc.c-torture/compile/stack-check-1.c: New test.
> +
> 2016-06-22 Richard Biener <rguenther@suse.de>
>
> * gcc.dg/vect/pr65947-1.c: Remove xfail.
> diff --git a/gcc/testsuite/gcc.c-torture/compile/stack-check-1.c b/gcc/testsuite/gcc.c-torture/compile/stack-check-1.c
> new file mode 100644
> index 00000000000..4058eb58709
> --- /dev/null
> +++ b/gcc/testsuite/gcc.c-torture/compile/stack-check-1.c
> @@ -0,0 +1,2 @@
> +/* { dg-additional-options "-fstack-check" } */
> +#include "20031023-1.c"
That test has:
/* { dg-require-effective-target untyped_assembly } */
which needs to be duplicated here (dejagnu isn't aware of the
#include and doesn't scan dg- directives in there).
Jakub
next prev parent reply other threads:[~2017-06-22 17:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 17:21 Jeff Law
2017-06-22 17:28 ` Jakub Jelinek [this message]
2017-06-23 14:58 ` Jeff Law
2017-06-22 17:29 ` Mike Stump
2017-06-23 11:15 ` Christophe Lyon
2017-06-23 15:03 ` 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=20170622172812.GA2123@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.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).