From: David Malcolm <dmalcolm@redhat.com>
To: "Basile Starynkevitch" <basile@starynkevitch.net>,
"Marc Nieper-Wißkirchen" <marc@nieper-wisskirchen.de>,
jit@gcc.gnu.org
Cc: David Malcolm <dmalcolm@redhat.com>
Subject: [PATCH 4/6] FIXME: non-working scanasm test
Date: Fri, 01 Jan 2016 00:00:00 -0000 [thread overview]
Message-ID: <1463170721-13825-4-git-send-email-dmalcolm@redhat.com> (raw)
In-Reply-To: <1463170721-13825-1-git-send-email-dmalcolm@redhat.com>
---
gcc/testsuite/gcc.dg/plugin/must-tail-call-3.c | 14 ++++++++++++++
gcc/testsuite/gcc.dg/plugin/plugin.exp | 3 ++-
2 files changed, 16 insertions(+), 1 deletion(-)
create mode 100644 gcc/testsuite/gcc.dg/plugin/must-tail-call-3.c
diff --git a/gcc/testsuite/gcc.dg/plugin/must-tail-call-3.c b/gcc/testsuite/gcc.dg/plugin/must-tail-call-3.c
new file mode 100644
index 0000000..b3d129d
--- /dev/null
+++ b/gcc/testsuite/gcc.dg/plugin/must-tail-call-3.c
@@ -0,0 +1,14 @@
+/* { dg-do compile } */
+
+extern int callee (int i);
+
+int __attribute__((noinline,noclone))
+caller (int i)
+{
+ return callee (i + 1);
+}
+
+/* FIXME: this is showing up as UNRESOLVED, with "output file does not exist"
+ scanasm.exp erroneously uses "must_tail_call_plugin" as the root name
+ of the test case, and hence "must_tail_call_plugin.s" as the $output_file. */
+/* { dg-final { scan-assembler-not "ret" } } */
diff --git a/gcc/testsuite/gcc.dg/plugin/plugin.exp b/gcc/testsuite/gcc.dg/plugin/plugin.exp
index 62f6797..688d59a 100644
--- a/gcc/testsuite/gcc.dg/plugin/plugin.exp
+++ b/gcc/testsuite/gcc.dg/plugin/plugin.exp
@@ -76,7 +76,8 @@ set plugin_test_list [list \
location-overflow-test-2.c } \
{ must_tail_call_plugin.c \
must-tail-call-1.c \
- must-tail-call-2.c } \
+ must-tail-call-2.c \
+ must-tail-call-3.c } \
]
foreach plugin_test $plugin_test_list {
--
1.8.5.3
prev parent reply other threads:[~2016-05-13 19:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-01 0:00 [PATCH 0/6] jit: Work-in-progress implementation of must-tail-call David Malcolm
2016-01-01 0:00 ` Marc Nieper-Wißkirchen
2016-01-01 0:00 ` [PATCH 1/6] FIXME: introduce can_implement_as_sibling_call_p David Malcolm
2016-01-01 0:00 ` [PATCH 6/6] FIXME: jit: add test of failing must-TCO David Malcolm
2016-01-01 0:00 ` [PATCH 2/6] FIXME: WIP on non-jit part of must-tail-call David Malcolm
2016-01-01 0:00 ` [PATCH 3/6] FIXME: WIP on jit " David Malcolm
2016-01-01 0:00 ` [PATCH 5/6] FIXME: initial support for gcc diagnostics as jit errors David Malcolm
2016-01-01 0:00 ` David Malcolm [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=1463170721-13825-4-git-send-email-dmalcolm@redhat.com \
--to=dmalcolm@redhat.com \
--cc=basile@starynkevitch.net \
--cc=jit@gcc.gnu.org \
--cc=marc@nieper-wisskirchen.de \
/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).