public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Tobias Burnus <burnus@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r14-4705] fortran/intrinsic.texi: Add 'intrinsic' to SIGNAL example Date: Wed, 18 Oct 2023 07:30:18 +0000 (GMT) [thread overview] Message-ID: <20231018073018.376FA385841B@sourceware.org> (raw) https://gcc.gnu.org/g:372c5da2153835baa95f232b917da81ea7445c7d commit r14-4705-g372c5da2153835baa95f232b917da81ea7445c7d Author: Tobias Burnus <tobias@codesourcery.com> Date: Tue Oct 17 19:35:18 2023 +0200 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. Diff: --- gcc/fortran/intrinsic.texi | 1 + 1 file changed, 1 insertion(+) diff --git a/gcc/fortran/intrinsic.texi b/gcc/fortran/intrinsic.texi index 0db557d5a38c..d1407186aea1 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)
reply other threads:[~2023-10-18 7:30 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=20231018073018.376FA385841B@sourceware.org \ --to=burnus@gcc.gnu.org \ --cc=gcc-cvs@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: linkBe 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).