From: Toon Moene <toon@moene.org>
To: gfortran <fortran@gcc.gnu.org>
Subject: Fwd: [PATCH 17/25] Fix Fortran STOP.
Date: Wed, 05 Sep 2018 16:55:00 -0000 [thread overview]
Message-ID: <c0630914-1252-1391-9bf9-f03434d46f5a@moene.org> (raw)
In-Reply-To: <3b1ee6252e6bc42be1886f45fd4512efda27bcbd.1536144068.git.ams@codesourcery.com>
[-- Attachment #1: Type: text/plain, Size: 614 bytes --]
-------- Forwarded Message --------
Subject: [PATCH 17/25] Fix Fortran STOP.
Date: Wed, 5 Sep 2018 12:51:18 +0100
From: ams@codesourcery.com
To: gcc-patches@gcc.gnu.org
The minimal libgfortran setup was created for NVPTX, but will also be
used by
AMD GCN.
This patch simply removes an assumption that NVPTX is the only user.
Specifically, NVPTX exit is broken, but AMD GCN exit works just fine.
2018-09-05 Andrew Stubbs <ams@codesourcery.com>
libgfortran/
* runtime/minimal.c (exit): Only work around nvptx bugs on nvptx.
---
libgfortran/runtime/minimal.c | 2 ++
1 file changed, 2 insertions(+)
[-- Attachment #2: 0017-Fix-Fortran-STOP.patch --]
[-- Type: text/x-patch, Size: 555 bytes --]
diff --git a/libgfortran/runtime/minimal.c b/libgfortran/runtime/minimal.c
index 0b1efeb..8940f97 100644
--- a/libgfortran/runtime/minimal.c
+++ b/libgfortran/runtime/minimal.c
@@ -197,10 +197,12 @@ sys_abort (void)
#define st_printf printf
#undef estr_write
#define estr_write printf
+#if __nvptx__
/* Map "exit" to "abort"; see PR85463 '[nvptx] "exit" in offloaded region
doesn't terminate process'. */
#undef exit
#define exit(...) do { abort (); } while (0)
+#endif
#undef exit_error
#define exit_error(...) do { abort (); } while (0)
next parent reply other threads:[~2018-09-05 16:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3b1ee6252e6bc42be1886f45fd4512efda27bcbd.1536144068.git.ams@codesourcery.com>
2018-09-05 16:55 ` Toon Moene [this message]
2018-09-05 17:06 ` Bernhard Reutner-Fischer
2018-09-05 18:09 ` Janne Blomqvist
2018-09-12 13:56 ` Andrew Stubbs
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=c0630914-1252-1391-9bf9-f03434d46f5a@moene.org \
--to=toon@moene.org \
--cc=fortran@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).