public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/24685] real(16) formatted input is broken for huge values Date: Fri, 21 Apr 2006 17:04:00 -0000 [thread overview] Message-ID: <20060421170410.6104.qmail@sourceware.org> (raw) In-Reply-To: <bug-24685-8500@http.gcc.gnu.org/bugzilla/> ------- Comment #17 from jakub at gcc dot gnu dot org 2006-04-21 17:04 ------- Subject: Bug 24685 Author: jakub Date: Fri Apr 21 17:04:04 2006 New Revision: 113137 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=113137 Log: PR libgfortran/24685 * io/write.c (MIN_FIELD_WIDTH, STR, STR1): Define. (output_float): Increase buffer sizes for IEEE quad and IBM extended long double. (write_real): Output REAL(16) as 1PG43.34E4 rather than 1PG40.31E4. Modified: branches/gcc-4_1-branch/libgfortran/ChangeLog branches/gcc-4_1-branch/libgfortran/io/write.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24685
next prev parent reply other threads:[~2006-04-21 17:04 UTC|newest] Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-11-05 19:34 [Bug libfortran/24685] New: real(10) " jblomqvi at cc dot hut dot fi 2005-11-05 23:24 ` [Bug libfortran/24685] " fxcoudert at gcc dot gnu dot org 2006-02-05 22:20 ` [Bug libfortran/24685] [4.1 only] " fxcoudert at gcc dot gnu dot org 2006-02-05 23:04 ` fxcoudert at gcc dot gnu dot org 2006-02-14 15:48 ` fxcoudert at gcc dot gnu dot org 2006-02-14 15:50 ` fxcoudert at gcc dot gnu dot org 2006-02-16 10:55 ` ebotcazou at gcc dot gnu dot org 2006-02-16 11:12 ` [Bug libfortran/24685] real(16) " fxcoudert at gcc dot gnu dot org 2006-02-16 17:44 ` pinskia at gcc dot gnu dot org 2006-02-23 17:44 ` sje at cup dot hp dot com 2006-03-15 7:29 ` ebotcazou at gcc dot gnu dot org 2006-03-15 16:22 ` jb at gcc dot gnu dot org 2006-03-15 16:44 ` sje at cup dot hp dot com 2006-03-16 8:30 ` jb at gcc dot gnu dot org 2006-04-01 21:34 ` ebotcazou at gcc dot gnu dot org 2006-04-01 21:35 ` ebotcazou at gcc dot gnu dot org 2006-04-10 12:03 ` jakub at gcc dot gnu dot org 2006-04-21 17:04 ` jakub at gcc dot gnu dot org [this message] 2006-04-21 17:22 ` jakub at gcc dot gnu dot org 2006-05-24 18:58 ` fxcoudert at gcc dot gnu dot org 2006-05-24 19:01 ` Andrew Pinski 2006-05-24 19:01 ` pinskia at physics dot uc dot edu 2006-05-24 20:35 ` fxcoudert at gcc dot gnu dot org 2007-05-25 19:50 ` jvdelisle at gcc dot gnu dot org 2007-05-26 17:51 ` dominiq at lps dot ens dot fr 2007-11-03 16:48 ` jvdelisle at gcc dot gnu dot org 2007-11-12 5:44 ` jvdelisle at gcc dot gnu dot org 2008-01-17 11:24 ` [Bug libfortran/24685] real(16) formatted input is broken for huge values (gfortran.dg/default_format_2.f90) burnus at gcc dot gnu dot org 2008-01-17 15:33 ` ebotcazou at gcc dot gnu dot org 2008-01-24 15:09 ` dominiq at lps dot ens dot fr 2008-01-25 15:47 ` dominiq at lps dot ens dot fr 2008-02-23 20:11 ` fxcoudert at gcc dot gnu dot org 2008-02-23 20:11 ` fxcoudert at gcc dot gnu dot org 2008-02-28 7:10 ` uros at gcc dot gnu dot org 2008-12-12 22:20 ` janis at gcc dot gnu dot org 2008-12-12 22:23 ` janis at gcc dot gnu dot org 2008-12-19 1:39 ` howarth at nitro dot med dot uc dot edu 2008-12-19 17:51 ` janis at gcc dot gnu dot org 2008-12-19 18:15 ` janis at gcc dot gnu dot org 2008-12-19 18:23 ` janis at gcc dot gnu dot 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=20060421170410.6104.qmail@sourceware.org \ --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: 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).