From: Alexander Monakov <amonakov@ispras.ru>
To: gcc-patches@gcc.gnu.org
Subject: [gomp-nvptx 7/7] nvptx backend: define STACK_SIZE_MODE
Date: Fri, 18 Mar 2016 17:49:00 -0000 [thread overview]
Message-ID: <1458323327-9908-8-git-send-email-amonakov@ispras.ru> (raw)
In-Reply-To: <1458323327-9908-1-git-send-email-amonakov@ispras.ru>
Default definition of STACK_SIZE_MODE is word_mode, which is DImode on NVPTX.
However, stack pointer mode matches pointer mode, so needs to be SImode on
32-bit NVPTX ABI. Define it to Pmode to fix 32-bit code generation.
* config/nvptx/nvptx.h (STACK_SIZE_MODE): Define.
---
gcc/ChangeLog.gomp-nvptx | 4 ++++
gcc/config/nvptx/nvptx.h | 1 +
2 files changed, 5 insertions(+)
diff --git a/gcc/config/nvptx/nvptx.h b/gcc/config/nvptx/nvptx.h
index 7810cca..6da4d06 100644
--- a/gcc/config/nvptx/nvptx.h
+++ b/gcc/config/nvptx/nvptx.h
@@ -83,6 +83,7 @@
#define POINTER_SIZE (TARGET_ABI64 ? 64 : 32)
#define Pmode (TARGET_ABI64 ? DImode : SImode)
+#define STACK_SIZE_MODE Pmode
/* Registers. Since ptx is a virtual target, we just define a few
hard registers for special purposes and leave pseudos unallocated.
next prev parent reply other threads:[~2016-03-18 17:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 17:48 [gomp-nvptx 0/7] Various fixes Alexander Monakov
2016-03-18 17:48 ` [gomp-nvptx 1/7] libgomp: remove paste error in gomp_team_barrier_wait_end Alexander Monakov
2016-03-18 17:48 ` [gomp-nvptx 4/7] nvptx backend: re-enable line info generation Alexander Monakov
2016-03-18 17:48 ` [gomp-nvptx 2/7] nvptx libgcc: use attribute shared Alexander Monakov
2016-03-18 17:49 ` [gomp-nvptx 3/7] libgomp plugin: make cuMemFreeHost error non-fatal Alexander Monakov
2016-03-18 17:49 ` Alexander Monakov [this message]
2016-03-18 17:49 ` [gomp-nvptx 5/7] nvptx backend: use POINTER_SIZE instead of BITS_PER_WORD Alexander Monakov
2016-03-18 18:13 ` [gomp-nvptx 6/7] nvptx backend: change mul.u32 to mul.lo.u32 Alexander Monakov
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=1458323327-9908-8-git-send-email-amonakov@ispras.ru \
--to=amonakov@ispras.ru \
--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).