public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paul Richard Thomas <paul.richard.thomas@gmail.com>
To: Thomas Koenig <tkoenig@netcologne.de>
Cc: "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
	gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch, fortran, doc] Explicitly mention undefined overflow
Date: Sun, 19 Mar 2023 13:12:09 +0000	[thread overview]
Message-ID: <CAGkQGiLL8h1COfqZ_BZ2pK1tKSbVduXh59X-4a=NLRF0WurPvQ@mail.gmail.com> (raw)
In-Reply-To: <eee8f01b-7e2c-c465-eaed-226714dc9655@netcologne.de>

[-- Attachment #1: Type: text/plain, Size: 653 bytes --]

Hi Thomas,

Yes, that's fine for trunk. I wonder if it is worth being explicit that
linear congruential pseudo-random number generators can and do fail at -O3?

Thanks for the doc patches!

Paul


On Sun, 19 Mar 2023 at 08:32, Thomas Koenig via Fortran <fortran@gcc.gnu.org>
wrote:

> Here's also an update on the docs to explicitly mention behavior
> on overflow.
>
> Maybe this will reach another 0.05% of users...
>
> OK for trunk?
>
> Best regards
>
>         Thomas
>
> gcc/fortran/ChangeLog:
>
>         * gfortran.texi: Mention behavior on overflow.
>


-- 
"If you can't explain it simply, you don't understand it well enough" -
Albert Einstein

  reply	other threads:[~2023-03-19 13:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-19  8:32 Thomas Koenig
2023-03-19 13:12 ` Paul Richard Thomas [this message]
2023-03-19 17:40   ` Thomas Koenig
2023-03-20  7:14     ` Thomas Koenig
2023-03-20 21:32       ` Harald Anlauf
2023-03-19 13:15 ` Andreas Schwab

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='CAGkQGiLL8h1COfqZ_BZ2pK1tKSbVduXh59X-4a=NLRF0WurPvQ@mail.gmail.com' \
    --to=paul.richard.thomas@gmail.com \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=tkoenig@netcologne.de \
    /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).