From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: FX <fxcoudert@gmail.com>
Cc: FX via Fortran <fortran@gcc.gnu.org>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Fortran: add IEEE_QUIET_* and IEEE_SIGNALING_* comparisons
Date: Fri, 02 Sep 2022 18:03:29 +0200 [thread overview]
Message-ID: <C9B91DC3-FDEA-4B17-B021-EEA927AE46D2@gmail.com> (raw)
In-Reply-To: <A0047024-91B8-44B3-A8FA-C8D9CE7DC998@gmail.com>
On 2 September 2022 17:54:00 CEST, FX <fxcoudert@gmail.com> wrote:
>Hi Bernhard,
>
>> Please do not call the non-standard abort, but use stop N.
>
>Is there a specific reason? It’s a well-documented GNU extension, and it’s useful because it can easily display a backtrace and give line info for the failure, unlike STOP.
>I’ll replace if there is consensus, but apart from aesthetics I don’t see why.
IIRC there was discussion about abort on the ML some years ago where folks decided to switch to stop N.
I don't think I participated in that discussion, maybe somebody remembers the reasoning or is able to find the thread.
thanks,
next prev parent reply other threads:[~2022-09-02 16:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-02 11:37 FX
2022-09-02 15:37 ` Bernhard Reutner-Fischer
2022-09-02 15:54 ` FX
2022-09-02 16:03 ` Bernhard Reutner-Fischer [this message]
2022-09-02 16:17 ` FX
2022-09-17 11:58 ` Mikael Morin
2023-06-06 19:29 FX Coudert
2023-06-08 12:26 ` Harald Anlauf
2023-06-10 15:21 ` FX Coudert
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=C9B91DC3-FDEA-4B17-B021-EEA927AE46D2@gmail.com \
--to=rep.dot.nop@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=fxcoudert@gmail.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).