From: Dimitar Dimitrov <dimitar@dinux.eu>
To: gcc-patches@gcc.gnu.org
Cc: Dimitar Dimitrov <dimitar@dinux.eu>
Subject: [PATCH v4 10/10] testsuite: Mark testsuite that PRU has different calling convention
Date: Thu, 06 Sep 2018 11:13:00 -0000 [thread overview]
Message-ID: <20180906111217.24365-11-dimitar@dinux.eu> (raw)
In-Reply-To: <20180906111217.24365-1-dimitar@dinux.eu>
For variadic functions, the last named and all anonymous arguments
are passed on stack. Regular functions pass arguments in registers.
gcc/testsuite/ChangeLog:
2018-08-29 Dimitar Dimitrov <dimitar@dinux.eu>
* gcc.dg/builtin-apply2.c: Skip for PRU.
* gcc.dg/torture/stackalign/builtin-apply-2.c: Ditto.
Signed-off-by: Dimitar Dimitrov <dimitar@dinux.eu>
---
gcc/testsuite/gcc.dg/builtin-apply2.c | 2 +-
gcc/testsuite/gcc.dg/torture/stackalign/builtin-apply-2.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/gcc/testsuite/gcc.dg/builtin-apply2.c b/gcc/testsuite/gcc.dg/builtin-apply2.c
index 3768caa5d5a..6ede0f3054b 100644
--- a/gcc/testsuite/gcc.dg/builtin-apply2.c
+++ b/gcc/testsuite/gcc.dg/builtin-apply2.c
@@ -1,7 +1,7 @@
/* { dg-do run } */
/* { dg-require-effective-target untyped_assembly } */
/* { dg-skip-if "Variadic funcs have all args on stack. Normal funcs have args in registers." { "avr-*-* nds32*-*-*" } } */
-/* { dg-skip-if "Variadic funcs use different argument passing from normal funcs." { "riscv*-*-*" } } */
+/* { dg-skip-if "Variadic funcs use different argument passing from normal funcs." { "riscv*-*-* pru-*-*" } } */
/* { dg-skip-if "Variadic funcs use Base AAPCS. Normal funcs use VFP variant." { arm*-*-* && arm_hf_eabi } } */
/* PR target/12503 */
diff --git a/gcc/testsuite/gcc.dg/torture/stackalign/builtin-apply-2.c b/gcc/testsuite/gcc.dg/torture/stackalign/builtin-apply-2.c
index d033010dc7c..8b6e693c0f2 100644
--- a/gcc/testsuite/gcc.dg/torture/stackalign/builtin-apply-2.c
+++ b/gcc/testsuite/gcc.dg/torture/stackalign/builtin-apply-2.c
@@ -9,7 +9,7 @@
/* arm_hf_eabi: Variadic funcs use Base AAPCS. Normal funcs use VFP variant.
avr: Variadic funcs don't pass arguments in registers, while normal funcs
do. */
-/* { dg-skip-if "Variadic funcs use different argument passing from normal funcs" { arm_hf_eabi || { avr-*-* riscv*-*-* } } } */
+/* { dg-skip-if "Variadic funcs use different argument passing from normal funcs" { arm_hf_eabi || { avr-*-* riscv*-*-* pru-*-* } } } */
/* { dg-skip-if "Variadic funcs have all args on stack. Normal funcs have args in registers." { nds32*-*-* } } */
/* { dg-require-effective-target untyped_assembly } */
--
2.11.0
next prev parent reply other threads:[~2018-09-06 11:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-06 11:12 [PATCH v4 00/10] New backend for the TI PRU processor Dimitar Dimitrov
2018-09-06 11:12 ` [PATCH v4 04/10] testsuite: Add check for overflowed IMEM region to testsuite Dimitar Dimitrov
2018-09-06 11:13 ` [PATCH v4 05/10] testsuite: Add check for unsupported TI ABI PRU features " Dimitar Dimitrov
2018-09-06 11:13 ` Dimitar Dimitrov [this message]
2018-09-06 11:13 ` [PATCH v4 08/10] testsuite: Mark that PRU has one-cycle jumps Dimitar Dimitrov
2018-09-06 11:13 ` [PATCH v4 03/10] testsuite: Add PRU tests Dimitar Dimitrov
2018-09-06 11:13 ` [PATCH v4 09/10] testsuite: Mark that PRU uses all function pointer bits Dimitar Dimitrov
2018-09-06 11:13 ` [PATCH v4 06/10] testsuite: Remove PRU from test cases requiring hosted environment Dimitar Dimitrov
2018-09-06 11:13 ` [PATCH v4 01/10] Initial TI PRU GCC port Dimitar Dimitrov
2018-09-13 13:13 ` Richard Sandiford
2018-09-22 10:23 ` Dimitar Dimitrov
2018-09-24 10:49 ` Richard Sandiford
2018-09-24 17:49 ` Jeff Law
2018-09-25 5:16 ` Dimitar Dimitrov
2018-09-06 11:13 ` [PATCH v4 07/10] testsuite: Define PRU stack usage Dimitar Dimitrov
2018-09-06 11:13 ` [PATCH v4 02/10] Initial TI PRU libgcc port Dimitar Dimitrov
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=20180906111217.24365-11-dimitar@dinux.eu \
--to=dimitar@dinux.eu \
--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).