[Bug fortran/25109] New: formatted reads with embedded blanks in input fields
Formatted reads with embedded blanks in the input fields do not appear to be working correctly for I and F edit descriptors. For example, using the edit descriptor I3 to read in the value of an integer variable where the input field contains 1 3 Yields the runtime error message Bad value during integer read Using the edit descriptor f5.0 for reading a double precision variable where the input field contains 1 3 5 produces the resulting assinged value of the variable of 1d0 Very odd. -- Summary: formatted reads with embedded blanks in input fields Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: brad dot finney at humboldt dot edu GCC build triplet: 4.2.0 20051126 GCC host triplet: i686-pc-mingw32 GCC target triplet: win32 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25109
[Bug fortran/25109] formatted reads with embedded blanks in input fields
--- Comment #2 from brad dot finney at humboldt dot edu 2005-11-27 00:00 --- Created an attachment (id=10347) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=10347&action=view) test code -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25109
[Bug fortran/25109] formatted reads with embedded blanks in input fields
--- Comment #3 from brad dot finney at humboldt dot edu 2005-11-27 00:04 --- (From update of attachment 10347) use input data 1 3 5 with inpter reads uncommented, use input data 1 3 -- brad dot finney at humboldt dot edu changed: What|Removed |Added Attachment #10347|test code |test code description|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25109
[Bug fortran/31553] New: incorrect processing of formatted character output
"a" edit descriptor for character output produces repeatable, but incorrect output in some situations when the width of the field is not explicitly specified in the edit descriptor, but is inferred from the number of characters in the write list item. -- Summary: incorrect processing of formatted character output Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: brad dot finney at humboldt dot edu GCC build triplet: 4.3.0 GCC host triplet: i386-pc-mingw32 GCC target triplet: i386-pc-mingw32 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31553
[Bug fortran/31553] incorrect processing of formatted character output
--- Comment #1 from brad dot finney at humboldt dot edu 2007-04-12 18:20 --- Created an attachment (id=13359) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13359&action=view) test program demonstrating bug behavior along with program output -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31553
[Bug fortran/31553] incorrect processing of formatted character output
--- Comment #2 from brad dot finney at humboldt dot edu 2007-04-12 18:22 --- same bug noted on version 4.0.3 (intel linux 64bit) noted. -- brad dot finney at humboldt dot edu changed: What|Removed |Added CC||brad dot finney at humboldt ||dot edu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31553
[Bug fortran/31553] incorrect processing of formatted character output
--- Comment #4 from brad dot finney at humboldt dot edu 2007-04-12 20:29 --- (In reply to comment #3) > Which version are you using under i386-pc-mingw32? (I see "Reported against > 4.3.0, however - see below.) > gcc version 4.3.0 20061021 I had not tried on the latest version, so I apologize for posting a problem that has already been corrected. > I'm asking because "4.0.3 (intel linux 64bit)" is very old. GCC 4.0.x > contained > the freshly added and still a bit buggy gfortran. One should use version > 4.1.x, > which is much more stable, or the 4.2.0 or 4.3.0 which contain even fewer > Fortran bugs. Binaries are available from: > http://gcc.gnu.org/wiki/GFortranBinaries > > Using > gfortran 4.1.3 20070302 (prerelease) > gfortran 4.2.0 20070412 (prerelease) > gfortran 4.3.0 20070412 (experimental) > I get the same result as with NAG f95, sunf95 and Intel ifort: > > (4(a,' | ')) > 1234 | 12345678 | 1234567890123456 | 12345678901234567890 | > 1234 | 12345678 | 1234567890123456 | 12345678901234567890 | > 1234 | 12345678 | 1234567890123456 | 12345678901234567890 | > 1234 | 12345678 | 1234567890123456 | 12345678901234567890 | > As do I with version 4.3.0 20070406 Thanks, and again sorry. I did check the list of bugs first, but didn't see one that seemed to fit. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31553
[Bug fortran/45575] New: ICE on missing module file
missing module file results in a fatal error noting the missing module, and
then an ICE in f951.
sample source
program testmytypes
use mytypes
implicit none
real(dp)::x=5.
write(*,"(e13.6,' squared = ',e13.6)")x,x**2
end program testmytypes
Output:
F:\brad\class\engr325>gfortran bugtest.f90
bugtest.f90:2.13:
use mytypes
1
Fatal Error: Can't open module file 'mytypes.mod' for reading at (1): No such
file or directory
gfortran: internal compiler error: Aborted (program f951)
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
--
Summary: ICE on missing module file
Product: gcc
Version: 4.6.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: brad dot finney at humboldt dot edu
GCC build triplet: i586-pc-mingw32
GCC host triplet: i586-pc-mingw32
GCC target triplet: i586-pc-mingw32
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45575
[Bug fortran/45575] ICE on missing module file
--- Comment #2 from brad dot finney at humboldt dot edu 2010-09-07 20:55 --- Subject: Re: ICE on missing module file burnus at gcc dot gnu dot org wrote: > --- Comment #1 from burnus at gcc dot gnu dot org 2010-09-07 15:09 > --- > Works with x86_64-unknown-linux-gnu (4.6.0 20100907 (experimental) [trunk > revision 163943]) > and also under i686-w64-mingw and x86_64-w64-mingw. > > A test with i586-pc-mingw32 is pending; Kai offered to do it. > > Brad, if possible, can you provide more information, i.e. which version of > MinGW32 exactly (if known, for me "gfortran -v" prints the version + the SVN > revision), where did you get the build from? D:\fortran>gfortran -v Using built-in specs. COLLECT_GCC=gfortran COLLECT_LTO_WRAPPER=c:/program files/gfortran/bin/../libexec/gcc/i586-pc-mingw32/4.6.0/lto-wrapper.exe Target: i586-pc-mingw32 Configured with: ../gcc-trunk/configure --prefix=/mingw --enable-languages=c,fortran --with-gmp=/home/brad/gfortran/dependencies --disable-werror --enable-threa ds --disable-nls --build=i586-pc-mingw32 --enable-libgomp --disable-shared --disable-win32-registry --with-dwarf2 --disable-sjlj-exceptions --enable-lto Thread model: win32 gcc version 4.6.0 20100620 (experimental) [trunk revision 161045] (GCC) I am fighting with gdb, and it is winning. I will try that part later. Brad > > Can you run the compiler in a debugger? Use: > gfortran -v bugtest.f90 > and search for the line with starts with /some/path/f95 and run then the > "f951" > line in a debugger, e.g. > gdb --args /some/path/to/f951 many, many, many options > and then in (gdb) > run > bt > and post the result of the backtrace (bt). > > -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45575
[Bug fortran/45575] ICE on missing module file
--- Comment #3 from brad dot finney at humboldt dot edu 2010-09-08 04:32 --- Subject: Re: ICE on missing module file On 9/7/2010 8:09 AM, burnus at gcc dot gnu dot org wrote: > --- Comment #1 from burnus at gcc dot gnu dot org 2010-09-07 15:09 > --- > Works with x86_64-unknown-linux-gnu (4.6.0 20100907 (experimental) [trunk > revision 163943]) > and also under i686-w64-mingw and x86_64-w64-mingw. > > A test with i586-pc-mingw32 is pending; Kai offered to do it. > > Brad, if possible, can you provide more information, i.e. which version of > MinGW32 exactly (if known, for me "gfortran -v" prints the version + the SVN > revision), where did you get the build from? > > Can you run the compiler in a debugger? Use: >gfortran -v bugtest.f90 > and search for the line with starts with /some/path/f95 and run then the > "f951" > line in a debugger, e.g. >gdb --args /some/path/to/f951 many, many, many options > and then in (gdb) >run >bt > and post the result of the backtrace (bt). > > Don't think this produced any useful information, but here is the gdb output F:\brad\class\engr325>gdb --args d:/gfortran/bin/../libexec/gcc/i586-pc-mingw32/4.6.0/f951.exe bugtest.f90 -quiet -dumpbase bugtest.f90 -mtune=pentium -march=pentium -auxbase bugtest -version -fintrinsic-modules-path d:/gfortran/bin/../lib/gcc/i586-pc-mingw32/4.6.0/finclude -o C:\tem GNU gdb 6.8 Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i686-pc-mingw32"... (no debugging symbols found) (gdb) run Starting program: d:/gfortran/bin/../libexec/gcc/i586-pc-mingw32/4.6.0/f951.exe bugtest.f90 -quiet -dumpbase bugtest.f90 -mtune=pentium -march=pentium -auxbase bugtest -version -fintrinsic-modules-path d:/gfortran/bin/../lib/gcc/i586-pc-mingw32/4.6.0/finclude -o C:\\temp\\bugtest.s [New thread 2108.0x908] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) GNU Fortran (GCC) version 4.6.0 20100620 (experimental) [trunk revision 161045] (i586-pc-mingw32) compiled by GNU C version 4.6.0 20100620 (experimental) [trunk revision 161045], GMP version 4.3.2, MPFR version 2.4.2, MPC version 0.8.2 GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096 GNU Fortran (GCC) version 4.6.0 20100620 (experimental) [trunk revision 161045] (i586-pc-mingw32) compiled by GNU C version 4.6.0 20100620 (experimental) [trunk revision 161045], GMP version 4.3.2, MPFR version 2.4.2, MPC version 0.8.2 GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096 bugtest.f90:2.13: use mytypes 1 Fatal Error: Can't open module file 'mytypes.mod' for reading at (1): No such file or directory Program exited with code 03. (gdb) bt No stack. (gdb) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45575
[Bug fortran/45575] ICE on missing module file
--- Comment #4 from brad dot finney at humboldt dot edu 2010-09-08 04:46 --- Subject: Re: ICE on missing module file On 9/7/2010 8:09 AM, burnus at gcc dot gnu dot org wrote: > --- Comment #1 from burnus at gcc dot gnu dot org 2010-09-07 15:09 > --- > Works with x86_64-unknown-linux-gnu (4.6.0 20100907 (experimental) [trunk > revision 163943]) > and also under i686-w64-mingw and x86_64-w64-mingw. > > A test with i586-pc-mingw32 is pending; Kai offered to do it. > > Brad, if possible, can you provide more information, i.e. which version of > MinGW32 exactly (if known, for me "gfortran -v" prints the version + the SVN > revision), where did you get the build from? Forgot to add, I built this version myself. Brad -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45575
