public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Joost.VandeVondele at mat dot ethz.ch" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/62245] gfortran miscompiles int() on mips
Date: Sun, 24 Aug 2014 12:33:00 -0000	[thread overview]
Message-ID: <bug-62245-4-SvMyHmDVkg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-62245-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62245

--- Comment #8 from Joost VandeVondele <Joost.VandeVondele at mat dot ethz.ch> ---
(In reply to Julian Taylor from comment #7)
> But the docs indicate that there is no undefined behavior.
> As I interpret them the result of int() is always well defined.
> If the documentation would not state what happens in the case of overflow it
> would be fine to not mention it, but as is one has to know the standard to
> know that this part of the documentation is wrong.

I'll submit a patchlet to clarify the wording in the docs (the issue is the use
of range vs magnitude, which suggests defining behavior in the case of
overflow).


  parent reply	other threads:[~2014-08-24 12:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-24 10:54 [Bug fortran/62245] New: " jtaylor.debian at googlemail dot com
2014-08-24 11:29 ` [Bug fortran/62245] " Joost.VandeVondele at mat dot ethz.ch
2014-08-24 11:32 ` jtaylor.debian at googlemail dot com
2014-08-24 11:35 ` Joost.VandeVondele at mat dot ethz.ch
2014-08-24 11:40 ` jtaylor.debian at googlemail dot com
2014-08-24 11:42 ` jtaylor.debian at googlemail dot com
2014-08-24 12:01 ` Joost.VandeVondele at mat dot ethz.ch
2014-08-24 12:03 ` jtaylor.debian at googlemail dot com
2014-08-24 12:33 ` Joost.VandeVondele at mat dot ethz.ch [this message]
2014-08-24 12:35 ` jtaylor.debian at googlemail dot com
2014-08-24 12:36 ` Joost.VandeVondele at mat dot ethz.ch
2014-08-24 15:21 ` kargl at gcc dot gnu.org
2014-09-05 13:40 ` vondele at gcc dot gnu.org

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=bug-62245-4-SvMyHmDVkg@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).