------- Comment #1 from jvdelisle at gcc dot gnu dot org 2007-07-08 19:12
-------
I believe this has been fixed in gfortran version 4.2 and 4.3. You can get
better results with these.
In the meantime, I think your test case has uncovered another issue.
$ ./a.out | hexdump
0000000 6261 2000 2020 2020 2020 2020 2020 2020
0000010 2020 2020 0a20
There is a oo in byte position 4. I will have to investigate further.
--
jvdelisle at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|unassigned at gcc dot gnu |jvdelisle at gcc dot gnu dot
|dot org |org
Status|UNCONFIRMED |ASSIGNED
Ever Confirmed|0 |1
Last reconfirmed|0000-00-00 00:00:00 |2007-07-08 19:12:08
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32678
