* [Bug fortran/44998] runtime error when reading complex*16 using formatted I/O [reopen bug 19064]
2010-07-20 7:25 [Bug fortran/44998] New: runtime error when reading complex*16 using formatted I/O [reopen bug 19064] rmlarsen at gmail dot com
@ 2010-07-20 7:30 ` rmlarsen at gmail dot com
2010-07-20 7:31 ` rmlarsen at gmail dot com
` (8 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: rmlarsen at gmail dot com @ 2010-07-20 7:30 UTC (permalink / raw)
To: gcc-bugs
------- Comment #1 from rmlarsen at gmail dot com 2010-07-20 07:30 -------
Created an attachment (id=21255)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=21255&action=view)
bug.f
small program provoking the bug.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44998
^ permalink raw reply [flat|nested] 11+ messages in thread* [Bug fortran/44998] runtime error when reading complex*16 using formatted I/O [reopen bug 19064]
2010-07-20 7:25 [Bug fortran/44998] New: runtime error when reading complex*16 using formatted I/O [reopen bug 19064] rmlarsen at gmail dot com
2010-07-20 7:30 ` [Bug fortran/44998] " rmlarsen at gmail dot com
@ 2010-07-20 7:31 ` rmlarsen at gmail dot com
2010-07-20 7:56 ` burnus at gcc dot gnu dot org
` (7 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: rmlarsen at gmail dot com @ 2010-07-20 7:31 UTC (permalink / raw)
To: gcc-bugs
------- Comment #2 from rmlarsen at gmail dot com 2010-07-20 07:31 -------
Created an attachment (id=21256)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=21256&action=view)
test1.dat
data file for test case.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44998
^ permalink raw reply [flat|nested] 11+ messages in thread* [Bug fortran/44998] runtime error when reading complex*16 using formatted I/O [reopen bug 19064]
2010-07-20 7:25 [Bug fortran/44998] New: runtime error when reading complex*16 using formatted I/O [reopen bug 19064] rmlarsen at gmail dot com
2010-07-20 7:30 ` [Bug fortran/44998] " rmlarsen at gmail dot com
2010-07-20 7:31 ` rmlarsen at gmail dot com
@ 2010-07-20 7:56 ` burnus at gcc dot gnu dot org
2010-07-20 8:00 ` dominiq at lps dot ens dot fr
` (6 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: burnus at gcc dot gnu dot org @ 2010-07-20 7:56 UTC (permalink / raw)
To: gcc-bugs
------- Comment #3 from burnus at gcc dot gnu dot org 2010-07-20 07:56 -------
> This is to re-open bug 19064.
> Version 4.4.3 of gfortran appears to be broken again
Seems to work here. At least on my x86_64-unknown-linux-gnu the test case of PR
19064 comment 0 seems to work with GCC
- 4.6.0 20100716 (experimental) [trunk revision 162255]
- 4.5.1 20100519 (prerelease) [gcc-4_5-branch revision 159556]
- 4.4.5 20100513 (prerelease) [gcc-4_4-branch revision 159367]
- 4.2.1
- 4.1.2 20070115
Therefore,
(a) Can you try with a newer version of gfortran,
cf. http://gcc.gnu.org/wiki/GFortranBinaries
(b) For the test file in PR 19064: Are there special line breaks (carriage
return vs. new line) or is there no tailing new line character? Or are there
tabs? Is the architecture still i686-pc-linux-gnu?
Regarding (a): One possibility could be that is was broken only for a short
time - though somehow I find this less likely for a release branch (like your
4.4.3) than for the trunk, but it is possible and does happen.
...
(b) is partially superseded by your attachments. Though, I still cannot
reproduce it.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44998
^ permalink raw reply [flat|nested] 11+ messages in thread* [Bug fortran/44998] runtime error when reading complex*16 using formatted I/O [reopen bug 19064]
2010-07-20 7:25 [Bug fortran/44998] New: runtime error when reading complex*16 using formatted I/O [reopen bug 19064] rmlarsen at gmail dot com
` (2 preceding siblings ...)
2010-07-20 7:56 ` burnus at gcc dot gnu dot org
@ 2010-07-20 8:00 ` dominiq at lps dot ens dot fr
2010-07-20 8:38 ` rmlarsen at gmail dot com
` (5 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: dominiq at lps dot ens dot fr @ 2010-07-20 8:00 UTC (permalink / raw)
To: gcc-bugs
------- Comment #4 from dominiq at lps dot ens dot fr 2010-07-20 08:00 -------
Works for me on powerpc-apple-darwin9 (4.2.4, 4.3.4, 4.4.2, 4.5.0, and trunk)
and x86_64-apple-darwin10.4 (4.4.4, 4.5.0, and trunk).
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44998
^ permalink raw reply [flat|nested] 11+ messages in thread* [Bug fortran/44998] runtime error when reading complex*16 using formatted I/O [reopen bug 19064]
2010-07-20 7:25 [Bug fortran/44998] New: runtime error when reading complex*16 using formatted I/O [reopen bug 19064] rmlarsen at gmail dot com
` (3 preceding siblings ...)
2010-07-20 8:00 ` dominiq at lps dot ens dot fr
@ 2010-07-20 8:38 ` rmlarsen at gmail dot com
2010-07-20 8:46 ` rmlarsen at gmail dot com
` (4 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: rmlarsen at gmail dot com @ 2010-07-20 8:38 UTC (permalink / raw)
To: gcc-bugs
------- Comment #5 from rmlarsen at gmail dot com 2010-07-20 08:38 -------
Thanks for the quick response. Let me clarify: The data file contains no
trailing newline or carriage return - if a newline is appended the problem
disappears.
My setup is (default Ubuntu 10.0.4 install):
Target: i486-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 4.4.3-4ubuntu5'
--with-bugurl=file:///usr/share/doc/gcc-4.4/README.Bugs
--enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared
--enable-multiarch --enable-linker-build-id --with-system-zlib
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--with-gxx-include-dir=/usr/include/c++/4.4 --program-suffix=-4.4 --enable-nls
--enable-clocale=gnu --enable-libstdcxx-debug --enable-plugin --enable-objc-gc
--enable-targets=all --disable-werror --with-arch-32=i486 --with-tune=generic
--enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu
--target=i486-linux-gnu
Thread model: posix
gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5)
I will try other versions of gfortran when I get a chance.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44998
^ permalink raw reply [flat|nested] 11+ messages in thread* [Bug fortran/44998] runtime error when reading complex*16 using formatted I/O [reopen bug 19064]
2010-07-20 7:25 [Bug fortran/44998] New: runtime error when reading complex*16 using formatted I/O [reopen bug 19064] rmlarsen at gmail dot com
` (4 preceding siblings ...)
2010-07-20 8:38 ` rmlarsen at gmail dot com
@ 2010-07-20 8:46 ` rmlarsen at gmail dot com
2010-07-20 9:05 ` burnus at gcc dot gnu dot org
` (3 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: rmlarsen at gmail dot com @ 2010-07-20 8:46 UTC (permalink / raw)
To: gcc-bugs
------- Comment #6 from rmlarsen at gmail dot com 2010-07-20 08:46 -------
BTW: One obvious difference is that my system is 32 bit (x86 vs. x86_64). I
don't have a x86_64 system handy today to test that hypothesis.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44998
^ permalink raw reply [flat|nested] 11+ messages in thread* [Bug fortran/44998] runtime error when reading complex*16 using formatted I/O [reopen bug 19064]
2010-07-20 7:25 [Bug fortran/44998] New: runtime error when reading complex*16 using formatted I/O [reopen bug 19064] rmlarsen at gmail dot com
` (5 preceding siblings ...)
2010-07-20 8:46 ` rmlarsen at gmail dot com
@ 2010-07-20 9:05 ` burnus at gcc dot gnu dot org
2010-07-20 9:08 ` dominiq at lps dot ens dot fr
` (2 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: burnus at gcc dot gnu dot org @ 2010-07-20 9:05 UTC (permalink / raw)
To: gcc-bugs
------- Comment #7 from burnus at gcc dot gnu dot org 2010-07-20 09:04 -------
(In reply to comment #5)
> gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5)
I think the problem was only present between the 4.4.2 release (2009-10-15) and
4.4.4 (2010-04-29).
Most likely it was caused by the commit for PR 43265 (2010-03-17, in 4.4.4 (!)
not in 4.4.3 - ?!?) and fixed as PR 43517 (2010-03-25). The 4.5 trunk was
affected from 2010-03-09 to 2010-03-25). But there were also a couple of other
commits.
* * *
(In reply to comment #6)
> BTW: One obvious difference is that my system is 32 bit (x86 vs. x86_64). I
> don't have a x86_64 system handy today to test that hypothesis.
Unlikely. Additionally, with "gfortran -m32" (which uses the x86 library) it
also works for me.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44998
^ permalink raw reply [flat|nested] 11+ messages in thread* [Bug fortran/44998] runtime error when reading complex*16 using formatted I/O [reopen bug 19064]
2010-07-20 7:25 [Bug fortran/44998] New: runtime error when reading complex*16 using formatted I/O [reopen bug 19064] rmlarsen at gmail dot com
` (6 preceding siblings ...)
2010-07-20 9:05 ` burnus at gcc dot gnu dot org
@ 2010-07-20 9:08 ` dominiq at lps dot ens dot fr
2010-08-09 0:02 ` rmlarsen at gmail dot com
2010-08-09 0:32 ` jvdelisle at gcc dot gnu dot org
9 siblings, 0 replies; 11+ messages in thread
From: dominiq at lps dot ens dot fr @ 2010-07-20 9:08 UTC (permalink / raw)
To: gcc-bugs
------- Comment #8 from dominiq at lps dot ens dot fr 2010-07-20 09:08 -------
My ppc build is 32 bit by default and I have checked that I don't have trailing
end of line.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44998
^ permalink raw reply [flat|nested] 11+ messages in thread* [Bug fortran/44998] runtime error when reading complex*16 using formatted I/O [reopen bug 19064]
2010-07-20 7:25 [Bug fortran/44998] New: runtime error when reading complex*16 using formatted I/O [reopen bug 19064] rmlarsen at gmail dot com
` (7 preceding siblings ...)
2010-07-20 9:08 ` dominiq at lps dot ens dot fr
@ 2010-08-09 0:02 ` rmlarsen at gmail dot com
2010-08-09 0:32 ` jvdelisle at gcc dot gnu dot org
9 siblings, 0 replies; 11+ messages in thread
From: rmlarsen at gmail dot com @ 2010-08-09 0:02 UTC (permalink / raw)
To: gcc-bugs
------- Comment #9 from rmlarsen at gmail dot com 2010-08-09 00:02 -------
burnus,
Thanks for investigating. I have verified that the bug is indeed fixed in
4.6.0:
gcc version 4.6.0 20100407 (experimental) [trunk revision 158083] (GCC)
Hope the fixed version makes it into Ubuntu soon... Any idea who to lean on to
encourage that?
I changed the status to FIXED. Is that the correct status to use for this
situation?
Rasmus
--
rmlarsen at gmail dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |FIXED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44998
^ permalink raw reply [flat|nested] 11+ messages in thread* [Bug fortran/44998] runtime error when reading complex*16 using formatted I/O [reopen bug 19064]
2010-07-20 7:25 [Bug fortran/44998] New: runtime error when reading complex*16 using formatted I/O [reopen bug 19064] rmlarsen at gmail dot com
` (8 preceding siblings ...)
2010-08-09 0:02 ` rmlarsen at gmail dot com
@ 2010-08-09 0:32 ` jvdelisle at gcc dot gnu dot org
9 siblings, 0 replies; 11+ messages in thread
From: jvdelisle at gcc dot gnu dot org @ 2010-08-09 0:32 UTC (permalink / raw)
To: gcc-bugs
------- Comment #10 from jvdelisle at gcc dot gnu dot org 2010-08-09 00:31 -------
Good
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44998
^ permalink raw reply [flat|nested] 11+ messages in thread