http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50105
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Possibly: |Possibly: [4.6/4.7
|[4.3/4.4/4.5/4.6/4.7 |Regression] I/O with g6.5 -
|Regression] I/O with g6.5 - |wrong number of "**" shown
|wrong number of "**" shown |
--- Comment #4 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-08-17
09:12:38 UTC ---
(In reply to comment #3)
> Maybe we can trace back the change in GFortran between 4.1 and 4.3 and find
> out
> why it was changed?
I think it was a mistake of mine: I was actually testing with GCC 4.7 as I
misloaded the module. (I use "module" to load different shell environment
settings.) The change seems to be much more recent:
GCC 4.7 uses in libgfortran/io/write_float.def's OUTPUT_FLOAT_FMT_G:
if (nb > 0 && !dtp->u.p.g0_no_blanks)\
...
if (result == FAILURE)\
pad = '*';\
This seems to have been added 2011-01-28 for PR 47285 in patch
http://gcc.gnu.org/ml/fortran/2011-01/msg00226.html and thus it should should
only affect GCC 4.6.x and the 4.7 trunk.
Assuming the standards guys agree that the old behaviour is correct, it is
probably sufficient to delete the two quoted lines.
