public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/57496] I/O: WRITE(*,*) HUGE(0_16) [REAL(10)+REAL(16)]: Gives SIGFPE with -ffpe-trap=overflow
Date: Mon, 03 Jun 2013 09:29:00 -0000	[thread overview]
Message-ID: <bug-57496-4-SHQIufzHnI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57496-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57496

--- Comment #3 from Tobias Burnus <burnus at gcc dot gnu.org> ---
Author: burnus
Date: Mon Jun  3 09:20:46 2013
New Revision: 199598

URL: http://gcc.gnu.org/viewcvs?rev=199598&root=gcc&view=rev
Log:
2013-06-01  Tobias Burnus  <burnus@net-b.de>

        PR fortran/57496
        * io/write_float.def (ISFINITE2Q, ISFINITE2, ISFINITE2L,
        * ISFINITE,
        SIGNBIT2Q, SIGNBIT2, SIGNBIT2L, SIGNBIT, ISNAN2Q, ISNAN2,
        ISNAN2L, ISNAN): New macros.
        (output_float_FMT_G_,WRITE_FLOAT): Use them.


Modified:
    trunk/libgfortran/ChangeLog
    trunk/libgfortran/io/write_float.def


  parent reply	other threads:[~2013-06-03  9:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-01  8:32 [Bug fortran/57496] New: " burnus at gcc dot gnu.org
2013-06-01 18:37 ` [Bug fortran/57496] " burnus at gcc dot gnu.org
2013-06-03  9:29 ` burnus at gcc dot gnu.org [this message]
2013-06-03  9:31 ` [Bug fortran/57496] I/O: WRITE(*,*) HUGE(0._10) gives " burnus at gcc dot gnu.org
2013-06-27  9:46 ` dominiq at lps dot ens.fr
2015-08-16 15:27 ` fxcoudert at gcc dot gnu.org
2015-08-16 15:31 ` [Bug libfortran/57496] " fxcoudert at gcc dot gnu.org
2015-08-24 16:32 ` fxcoudert at gcc dot gnu.org
2015-08-24 16:34 ` fxcoudert 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-57496-4-SHQIufzHnI@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).