From: Tobias Burnus <tobias@codesourcery.com>
To: Harald Anlauf <anlauf@gmx.de>,
gcc-patches <gcc-patches@gcc.gnu.org>,
fortran <fortran@gcc.gnu.org>
Subject: Re: [patch] fortran/intrinsic.texi: Improve SIGNAL intrinsic entry
Date: Tue, 17 Oct 2023 19:36:38 +0200 [thread overview]
Message-ID: <65469650-12cf-4199-ba04-59bee081298d@codesourcery.com> (raw)
In-Reply-To: <4b56e2ca-0af1-4747-a90a-0eac16c1b82e@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 541 bytes --]
Hi Harald,
On 17.10.23 19:02, Harald Anlauf wrote:
> your latest patch - which you already pushed - removes the
> intrinsic declaration of signal.
Only to 'signal' or also to 'sleep'? I have now added both in the attach
patch.
(Not yet committed.)
Tobias
-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955
[-- Attachment #2: 0001-fortran-intrinsic.texi-Add-intrinsic-to-SIGNAL-examp.patch --]
[-- Type: text/x-patch, Size: 863 bytes --]
From bad72a07e572e4e0ac5ae9c25b9a234d98b1258f Mon Sep 17 00:00:00 2001
From: Tobias Burnus <tobias@codesourcery.com>
Date: Tue, 17 Oct 2023 19:35:18 +0200
Subject: [PATCH] fortran/intrinsic.texi: Add 'intrinsic' to SIGNAL example
gcc/fortran/ChangeLog:
* intrinsic.texi (signal): Add 'intrinsic :: signal, sleep' to
the example to make it safer.
---
gcc/fortran/intrinsic.texi | 1 +
1 file changed, 1 insertion(+)
diff --git a/gcc/fortran/intrinsic.texi b/gcc/fortran/intrinsic.texi
index 0db557d5a38..d1407186aea 100644
--- a/gcc/fortran/intrinsic.texi
+++ b/gcc/fortran/intrinsic.texi
@@ -13214,6 +13214,7 @@ contains
end module
program test_signal
use m_handler
+ intrinsic :: signal, sleep
call signal (12, handler_print) ! 12 = SIGUSR2 (on some systems)
call signal (10, 1) ! 10 = SIGUSR1 and 1 = SIG_IGN (on some systems)
--
2.34.1
next prev parent reply other threads:[~2023-10-17 17:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 17:11 [patch] fortran/intrinsic.texi: Add 'passed by value' to signal handler Tobias Burnus
2023-10-16 18:31 ` Harald Anlauf
2023-10-16 18:37 ` Steve Kargl
2023-10-17 7:47 ` [patch] fortran/intrinsic.texi: Improve SIGNAL intrinsic entry (was: [patch] fortran/intrinsic.texi: Add 'passed by value' to signal handler) Tobias Burnus
2023-10-17 17:02 ` [patch] fortran/intrinsic.texi: Improve SIGNAL intrinsic entry Harald Anlauf
2023-10-17 17:36 ` Tobias Burnus [this message]
2023-10-17 18:05 ` Harald Anlauf
2023-10-17 11:26 ` [patch] fortran/intrinsic.texi: Add 'passed by value' to signal handler Stanislav Maslovski
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=65469650-12cf-4199-ba04-59bee081298d@codesourcery.com \
--to=tobias@codesourcery.com \
--cc=anlauf@gmx.de \
--cc=fortran@gcc.gnu.org \
--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).