Commit d785f6a3 by Janne Blomqvist

PR 48488 Fix comments

From-SVN: r173169
parent f4c31037
2011-04-29 Janne Blomqvist <jb@gcc.gnu.org>
PR libfortran/48488
* io/write.c (write_real, write_real_g0): Update comments.
2011-04-29 Jerry DeLisle <jvdelisle@gcc.gnu.org> 2011-04-29 Jerry DeLisle <jvdelisle@gcc.gnu.org>
Janne Blomqvist <jb@gcc.gnu.org> Janne Blomqvist <jb@gcc.gnu.org>
......
...@@ -1456,10 +1456,15 @@ set_fnode_default (st_parameter_dt *dtp, fnode *f, int length) ...@@ -1456,10 +1456,15 @@ set_fnode_default (st_parameter_dt *dtp, fnode *f, int length)
break; break;
} }
} }
/* Output a real number with default format.
This is 1PG14.7E2 for REAL(4), 1PG23.15E3 for REAL(8), /* Output a real number with default format. This is 1PG16.9E2 for
1PG28.19E4 for REAL(10) and 1PG43.34E4 for REAL(16). */ REAL(4), 1PG25.17E3 for REAL(8), 1PG30.21E4 for REAL(10) and
// FX -- FIXME: should we change the default format for __float128-real(16)? 1PG45.36E4 for REAL(16). The exception is that the Fortran standard
requires outputting an extra digit when the scale factor is 1 and
when the magnitude of the value is such that E editing is
used. However, gfortran compensates for this, and thus for list
formatted the same number of significant digits is generated both
when using F and E editing. */
void void
write_real (st_parameter_dt *dtp, const char *source, int length) write_real (st_parameter_dt *dtp, const char *source, int length)
...@@ -1472,6 +1477,8 @@ write_real (st_parameter_dt *dtp, const char *source, int length) ...@@ -1472,6 +1477,8 @@ write_real (st_parameter_dt *dtp, const char *source, int length)
dtp->u.p.scale_factor = org_scale; dtp->u.p.scale_factor = org_scale;
} }
/* Similar to list formatted REAL output, for kPG0 where k > 0 we
compensate for the extra digit. */
void void
write_real_g0 (st_parameter_dt *dtp, const char *source, int length, int d) write_real_g0 (st_parameter_dt *dtp, const char *source, int length, int d)
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment