From: Tom de Vries <Tom_deVries@mentor.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: [nvptx, committed, PR79939] Disable constant pool for nvptx
Date: Sun, 11 Jun 2017 21:58:00 -0000 [thread overview]
Message-ID: <f59cb1d2-ad77-0b28-e0d9-5d04af47844a@mentor.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 209 bytes --]
Hi,
this patch fixes PR79939, a cc1 hang while trying to emit a constant in
the constant pool.
Fixed by disabling the constant pool for nvptx.
Tested on target nvptx.
Committed as obvious.
Thanks,
- Tom
[-- Attachment #2: 0001-Disable-constant-pool-for-nvptx.patch --]
[-- Type: text/x-patch, Size: 1123 bytes --]
Disable constant pool for nvptx
2017-06-11 Tom de Vries <tom@codesourcery.com>
PR target/79939
* config/nvptx/nvptx.c (nvptx_cannot_force_const_mem): New function.
Return true.
(TARGET_CANNOT_FORCE_CONST_MEM): Redefine to
nvptx_cannot_force_const_mem.
---
gcc/config/nvptx/nvptx.c | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/gcc/config/nvptx/nvptx.c b/gcc/config/nvptx/nvptx.c
index 2eb5570..daeec27 100644
--- a/gcc/config/nvptx/nvptx.c
+++ b/gcc/config/nvptx/nvptx.c
@@ -5328,6 +5328,13 @@ nvptx_goacc_reduction (gcall *call)
}
}
+static bool
+nvptx_cannot_force_const_mem (machine_mode mode ATTRIBUTE_UNUSED,
+ rtx x ATTRIBUTE_UNUSED)
+{
+ return true;
+}
+
#undef TARGET_OPTION_OVERRIDE
#define TARGET_OPTION_OVERRIDE nvptx_option_override
@@ -5442,6 +5449,9 @@ nvptx_goacc_reduction (gcall *call)
#undef TARGET_GOACC_REDUCTION
#define TARGET_GOACC_REDUCTION nvptx_goacc_reduction
+#undef TARGET_CANNOT_FORCE_CONST_MEM
+#define TARGET_CANNOT_FORCE_CONST_MEM nvptx_cannot_force_const_mem
+
struct gcc_target targetm = TARGET_INITIALIZER;
#include "gt-nvptx.h"
reply other threads:[~2017-06-11 21:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=f59cb1d2-ad77-0b28-e0d9-5d04af47844a@mentor.com \
--to=tom_devries@mentor.com \
--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).