From: Dimitar Dimitrov <dimitar@dinux.eu>
To: gcc-patches@gcc.gnu.org
Cc: Dimitar Dimitrov <dimitar@dinux.eu>
Subject: [PATCH v3 09/10] testsuite: Mark that PRU uses all function pointer bits
Date: Thu, 16 Aug 2018 04:50:00 -0000 [thread overview]
Message-ID: <20180816044959.12320-10-dimitar@dinux.eu> (raw)
In-Reply-To: <20180816044959.12320-1-dimitar@dinux.eu>
gcc/testsuite/ChangeLog:
2018-07-27 Dimitar Dimitrov <dimitar@dinux.eu>
* g++.old-deja/g++.abi/ptrmem.C: Add PRU to list.
Signed-off-by: Dimitar Dimitrov <dimitar@dinux.eu>
---
gcc/testsuite/g++.old-deja/g++.abi/ptrmem.C | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gcc/testsuite/g++.old-deja/g++.abi/ptrmem.C b/gcc/testsuite/g++.old-deja/g++.abi/ptrmem.C
index 341735879c5..bda7960d8a2 100644
--- a/gcc/testsuite/g++.old-deja/g++.abi/ptrmem.C
+++ b/gcc/testsuite/g++.old-deja/g++.abi/ptrmem.C
@@ -7,7 +7,7 @@
function. However, some platforms use all bits to encode a
function pointer. Such platforms use the lowest bit of the delta,
that is shifted left by one bit. */
-#if defined __MN10300__ || defined __SH5__ || defined __arm__ || defined __thumb__ || defined __mips__ || defined __aarch64__
+#if defined __MN10300__ || defined __SH5__ || defined __arm__ || defined __thumb__ || defined __mips__ || defined __aarch64__ || defined __PRU__
#define ADJUST_PTRFN(func, virt) ((void (*)())(func))
#define ADJUST_DELTA(delta, virt) (((delta) << 1) + !!(virt))
#else
--
2.11.0
next prev parent reply other threads:[~2018-08-16 4:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-16 4:50 [PATCH v3 00/10] New backend for the TI PRU processor Dimitar Dimitrov
2018-08-16 4:50 ` [PATCH v3 08/10] testsuite: Mark that PRU has one-cycle jumps Dimitar Dimitrov
2018-08-16 4:50 ` [PATCH v3 06/10] testsuite: Remove PRU from test cases requiring hosted environment Dimitar Dimitrov
2018-08-16 4:50 ` [PATCH v3 05/10] testsuite: Add check for unsupported TI ABI PRU features to testsuite Dimitar Dimitrov
2018-08-16 4:50 ` [PATCH v3 04/10] testsuite: Add check for overflowed IMEM region " Dimitar Dimitrov
2018-08-16 4:50 ` [PATCH v3 10/10] testsuite: Mark testsuite that PRU has different calling convention Dimitar Dimitrov
2018-08-16 4:50 ` [PATCH v3 01/10] Initial TI PRU GCC port Dimitar Dimitrov
2018-08-20 17:12 ` Jeff Law
2018-08-23 5:09 ` Dimitar Dimitrov
2018-08-29 10:03 ` Dimitar Dimitrov
2018-08-16 4:50 ` [PATCH v3 07/10] testsuite: Define PRU stack usage Dimitar Dimitrov
2018-08-16 4:50 ` Dimitar Dimitrov [this message]
2018-08-16 4:50 ` [PATCH v3 02/10] Initial TI PRU libgcc port Dimitar Dimitrov
2018-08-20 14:37 ` Jeff Law
2018-08-16 4:50 ` [PATCH v3 03/10] testsuite: Add PRU tests Dimitar Dimitrov
2018-08-20 14:34 ` 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=20180816044959.12320-10-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).