[Bug libfortran/26890] SIZE parameter interacts with same variable in IO list character length specification.
-- 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|-00-00 00:00:00 |2006-04-09 05:30:33 date|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26890
[Bug libfortran/27107] New: Make dependency on io/io.h broken
When revising libgfortran/io/io.h by itself, make does not recompile source files that include io.h causing erroneous builds. To get files recompiled that depend on io.h one must 'touch' the sourcefiles. -- Summary: Make dependency on io/io.h broken Product: gcc Version: 4.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libfortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jvdelisle at gcc dot gnu dot org GCC host triplet: i686-pc-linux-gno http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27107
[Bug fortran/27112] Rejects to call a generic procedure by argument keywords.
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2006-04-11 05:02 --- Intel agrees with gfortran: fortcom: Error: foofoo.f90, line 25: The type/rank/keyword signature for this specific procedure matches another specific procedure that shares the same generic-spec. [FOO2] use m2 --^ fortcom: Error: foofoo.f90, line 24: The type/rank/keyword signature for this specific procedure matches another specific procedure that shares the same generic-spec. [FOO1] use m1 --^ compilation aborted for foofoo.f90 (code 1) Also Lahey checker agrees: Checking file SOURCE.F90. Checking program unit M1 at line 1. Checking program unit M2 at line 12. Checking program unit TEST at line 23. Line 25, file SOURCE.F90 use m2 | FATAL -- The arguments for procedures (FOO2) and (FOO1) allow references to the generic procedure to be ambiguous (see "Procedure Interfaces" in your Fortran 90 language reference). Encountered 1 error, 0 warnings in file SOURCE.F90. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27112
[Bug fortran/27112] Rejects to call a generic procedure by argument keywords.
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2006-04-12 01:24 --- I only have access to the free versions of Intel version 8.0 and version 9.0 and both gave aborted compilation on the test case for ambiguity. Next step is to check the standards, which I presume Paul has done. :) I see that the Intel compiler Iguchi has gives a warning. Paul only found one other compiler that accepts it. Perhaps this behavior is an extension to the standard? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27112
[Bug fortran/27112] Rejects to call a generic procedure by argument keywords.
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2006-04-12 02:25 --- Looking at the standard: Looking in the F95 Standard: " NOTE 12.4 The dummy argument names may be different because the name of a dummy argument is not a characteristic. " Also, allowing the use of a keyword to resolve the ambigity conflicts with the optional use of keywords. In the test case given you can not call foo without a keyword which would make the keyword use mandatory which the standard says is optional. I also checked one of my Fortran 90 books. It says that the type and number of arguments are used to determine the function or procedure to call. It does not say anything about keywords. All the examples show disambiguation by argument type. Note: I am not a standards authority, this is just all I could find. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27112
[Bug fortran/27138] gfortran: read(*,*) myInt advances only one character on error
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2006-04-13 00:22 --- I will investigate. -- 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|-00-00 00:00:00 |2006-04-13 00:22:23 date|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27138
[Bug fortran/27138] gfortran: read(*,*) myInt advances only one character on error
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2006-04-13 04:26 --- I have looked this over. Its a matter of what behavior is acceptable for each type of error we get. My interpretation of your testcase is that we should do a next_record when we detect the error before we do the generate_error if we are in ADVANCE_YES. So if its an error due to an I/O problem such as hardware failure we will just fail out like now. If its a "content of the file" error we do a next_record before going into th error handling code. This will presumably take us past the current line, ready for another read. I just wonder if this is the universal behavior we should have. Regardless, I will see if I can work up a patch and give it a spin. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27138
[Bug fortran/26766] [F2003] Recursive I/O still (again) broken
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2006-04-13 06:25 --- Subject: Bug 26766 Author: jvdelisle Date: Thu Apr 13 06:24:58 2006 New Revision: 112914 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=112914 Log: 2006-04-12 Jerry DeLisle <[EMAIL PROTECTED]> PR libgfortran/26766 * io/io.h: Add bit to identify associated unit as internal. * io/unit.c (get_external_unit): Renamed the find_unit_1 function to reflect the external unit functionality vs internal unit. (get_internal_unit): New function to allocate and initialize an internal unit structure. (get_unit): Use get_internal_unit and get_external_unit. (is_internal_unit): Revised to use new bit added in io.h. * io/transfer.c (data_transfer_init): Fix line width. (st_read_done): Free memory allocated for internal unit. (st_write_done): Add test to only flush and truncate when not an internal unit. Free memory allocated for internal unit. Modified: trunk/libgfortran/ChangeLog trunk/libgfortran/io/io.h trunk/libgfortran/io/transfer.c trunk/libgfortran/io/unit.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26766
[Bug fortran/26766] [F2003] Recursive I/O still (again) broken
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2006-04-13 06:30 --- Subject: Bug 26766 Author: jvdelisle Date: Thu Apr 13 06:30:04 2006 New Revision: 112915 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=112915 Log: 2006-04-12 Jerry DeLisle <[EMAIL PROTECTED]> PR libgfortran/26766 * gfortran.dg/write_recursive.f90: New test. Added: trunk/gcc/testsuite/gfortran.dg/write_recursive.f90 Modified: trunk/gcc/testsuite/ChangeLog -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26766
[Bug fortran/27138] gfortran: read(*,*) myInt advances only one character on error
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2006-04-13 07:20 --- The "engima" referred to in comment#2 is because it is a list directed read and commas and spaces are deliminators. If you turn this into a read with a format of '(a)' you get the whole string. I am still working on the remaining dubious behavior. :) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27138
[Bug fortran/27112] Rejects to call a generic procedure by argument keywords.
--- Comment #7 from jvdelisle at gcc dot gnu dot org 2006-04-13 23:54 --- This is not a compiler bug. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||INVALID http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27112
[Bug libfortran/26890] SIZE parameter interacts with same variable in IO list character length specification.
--- Comment #14 from jvdelisle at gcc dot gnu dot org 2006-04-14 02:31 --- Subject: Bug 26890 Author: jvdelisle Date: Fri Apr 14 02:31:28 2006 New Revision: 112943 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=112943 Log: 2006-04-14 Jerry DeLisle <[EMAIL PROTECTED]> PR libgfortran/26890 * io/io.h: Add size_used to st_parameter_dt. *io/transfer.c (data_transfer_init): Initialize size_used to zero. (read_sf): Use size_used. (read_block): Likewise. (read_block_direct): Likewise. (write_block): Likewise. (write_buf): Likewise and eliminate erroneous FAILURE return. (finalize_transfer): Assign value of size_used to *dtp->size. Modified: branches/gcc-4_1-branch/libgfortran/ChangeLog branches/gcc-4_1-branch/libgfortran/io/io.h branches/gcc-4_1-branch/libgfortran/io/transfer.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26890
[Bug target/26980] g++.old-deja/g++.other/init5.C execution test fails
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2006-04-14 02:36 --- Subject: Bug 26980 Author: jvdelisle Date: Fri Apr 14 02:36:49 2006 New Revision: 112944 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=112944 Log: 2006-04-14 Jerry DeLisle <[EMAIL PROTECTED]> PR libgfortran/26980 * gfortran.dg/read_size_noadvance.f90: New test. Added: branches/gcc-4_1-branch/gcc/testsuite/gfortran.dg/read_size_noadvance.f90 Modified: branches/gcc-4_1-branch/gcc/testsuite/ChangeLog -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26980
[Bug libfortran/26890] SIZE parameter interacts with same variable in IO list character length specification.
--- Comment #15 from jvdelisle at gcc dot gnu dot org 2006-04-14 03:14 --- Testcase was committed to 4.1 branch as well, but I typoed the pr number so it did not register commit here. Fixed on 4.1 and trunk. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added Target Milestone|--- |4.1.1 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26890
[Bug libfortran/26890] SIZE parameter interacts with same variable in IO list character length specification.
--- Comment #16 from jvdelisle at gcc dot gnu dot org 2006-04-14 03:16 --- Closing -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26890
[Bug fortran/27138] gfortran: read(*,*) myInt advances only one character on error
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2006-04-14 05:50 --- Created an attachment (id=11263) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=11263&action=view) Proposed Patch This is a proposed patch you can try out while I work up a more complete test case. The example given only addresses an integer read. The same thing happens for real, complex, or logical I think. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27138
[Bug testsuite/25336] Identical tests: gfortran.dg/g77/20030115-1.f gfortran.dg/g77/pr9258.f
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2006-04-15 04:51 --- Subject: Bug 25336 Author: jvdelisle Date: Sat Apr 15 04:51:39 2006 New Revision: 112967 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=112967 Log: 2006-04-15 Jerry DeLisle <[EMAIL PROTECTED]> PR fortran/25336 * gfortran/dg/g77/20030115-1.f: Delete duplicate test. Removed: trunk/gcc/testsuite/gfortran.dg/g77/20030115-1.f Modified: trunk/gcc/testsuite/ChangeLog -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25336
[Bug testsuite/25336] Identical tests: gfortran.dg/g77/20030115-1.f gfortran.dg/g77/pr9258.f
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2006-04-15 04:52 --- Deleted duplicate file on trunk. No need to do so on any branches. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25336
[Bug libfortran/20257] Fortran runtime error: End of record occurs when writing large arrays
--- Comment #8 from jvdelisle at gcc dot gnu dot org 2006-04-15 07:15 --- I have the beginnings of a patch going. It covers formatted write to stdout. Seems to work OK. I just need to extend the concept to the other cases. -- 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|NEW |ASSIGNED Last reconfirmed|2005-12-28 06:36:18 |2006-04-15 07:15:20 date|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20257
[Bug fortran/27138] gfortran: read(*,*) myInt advances only one character on error
--- Comment #8 from jvdelisle at gcc dot gnu dot org 2006-04-17 02:33 --- Subject: Bug 27138 Author: jvdelisle Date: Mon Apr 17 02:33:51 2006 New Revision: 112999 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=112999 Log: 2006-04-14 Jerry DeLisle <[EMAIL PROTECTED]> PR libgfortran/27138 * io/list_read.c (eat_line): New function. (parse_repeat): Use new function and free_saved. (read_logical): Same. (read_integer): Use new function. (parse_real): Use nml_bad_return and new function. (read_complex): Use new function and free_saved. (read_real): Same. Modified: trunk/libgfortran/ChangeLog trunk/libgfortran/io/list_read.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27138
[Bug fortran/27138] gfortran: read(*,*) myInt advances only one character on error
--- Comment #9 from jvdelisle at gcc dot gnu dot org 2006-04-17 02:37 --- Subject: Bug 27138 Author: jvdelisle Date: Mon Apr 17 02:37:15 2006 New Revision: 113000 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=113000 Log: 2006-04-16 Jerry DeLisle <[EMAIL PROTECTED]> PR libgfortran/27138 * gfortran.dg/read_bad_advance.f90: New test. Added: trunk/gcc/testsuite/gfortran.dg/read_bad_advance.f90 Modified: trunk/gcc/testsuite/ChangeLog -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27138
[Bug fortran/26766] [F2003] Recursive I/O still (again) broken
--- Comment #7 from jvdelisle at gcc dot gnu dot org 2006-04-17 04:31 --- Subject: Bug 26766 Author: jvdelisle Date: Mon Apr 17 04:31:18 2006 New Revision: 113002 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=113002 Log: 2006-04-16 Jerry DeLisle <[EMAIL PROTECTED]> PR libgfortran/26766 * io/io.h: Add bit to identify associated unit as internal. * io/unit.c (get_external_unit): Renamed the find_unit_1 function to reflect the external unit functionality vs internal unit. (get_internal_unit): New function to allocate and initialize an internal unit structure. (get_unit): Use get_internal_unit and get_external_unit. (is_internal_unit): Revised to use new bit added in io.h. * io/transfer.c (data_transfer_init): Fix line width. (st_read_done): Free memory allocated for internal unit. (st_write_done): Add test to only flush and truncate when not an internal unit. Free memory allocated for internal unit. Modified: branches/gcc-4_1-branch/libgfortran/ChangeLog branches/gcc-4_1-branch/libgfortran/io/io.h branches/gcc-4_1-branch/libgfortran/io/transfer.c branches/gcc-4_1-branch/libgfortran/io/unit.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26766
[Bug fortran/26766] [F2003] Recursive I/O still (again) broken
--- Comment #8 from jvdelisle at gcc dot gnu dot org 2006-04-17 04:34 --- Subject: Bug 26766 Author: jvdelisle Date: Mon Apr 17 04:33:59 2006 New Revision: 113003 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=113003 Log: 2006-04-16 Jerry DeLisle <[EMAIL PROTECTED]> PR libgfortran/26766 * gfortran.dg/write_recursive.f90: New test. Added: branches/gcc-4_1-branch/gcc/testsuite/gfortran.dg/write_recursive.f90 Modified: branches/gcc-4_1-branch/gcc/testsuite/ChangeLog -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26766
[Bug fortran/26766] [F2003] Recursive I/O still (again) broken
--- Comment #9 from jvdelisle at gcc dot gnu dot org 2006-04-17 04:38 --- Fixed on 4.1 and trunk -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26766
[Bug c/27191] New: ice on bootstrap - dwarf2out.c
/home/jerry/gcc/4.2/./gcc/xgcc -B/home/jerry/gcc/4.2/./gcc/ -B/home/jerry/gcc/usr/i686-pc-linux-gnu/bin/ -B/home/jerry/gcc/usr/i686-pc-linux-gnu/lib/ -isystem /home/jerry/gcc/usr/i686-pc-linux-gnu/include -isystem /home/jerry/gcc/usr/i686-pc-linux-gnu/sys-include -O2 -O2 -g -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -isystem ./include -fPIC -g -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -msse -c \ ../../main/gcc/config/i386/crtfastmath.c \ -o crtfastmath.o /bin/sh ../../main/gcc/../move-if-change tmp-macro_list macro_list ../../main/gcc/config/i386/crtfastmath.c:110: internal compiler error: in prune_unused_types_update_strings, at dwarf2out.c:14009 Please submit a full bug report, with preprocessed source if appropriate. See http://gcc.gnu.org/bugs.html> for instructions. make[3]: *** [crtfastmath.o] Error 1 -- Summary: ice on bootstrap - dwarf2out.c Product: gcc Version: 4.2.0 Status: UNCONFIRMED Severity: blocker Priority: P3 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jvdelisle at gcc dot gnu dot org GCC host triplet: i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27191
[Bug c/27191] ice on bootstrap - dwarf2out.c
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2006-04-18 03:51 --- I just found this already reported. *** This bug has been marked as a duplicate of 27188 *** -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||DUPLICATE http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27191
[Bug debug/27188] [4.2 Regression] libgcc2.c:382: internal compiler error: in prune_unused_types_update_strings, at dwarf2out.c:14009
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2006-04-18 03:51 --- *** Bug 27191 has been marked as a duplicate of this bug. *** -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added CC||jvdelisle at gcc dot gnu dot ||org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27188
[Bug fortran/26106] [meta-bug] Gfortran can't compile tonto
--- Comment #19 from jvdelisle at gcc dot gnu dot org 2006-04-20 06:21 --- Created an attachment (id=11300) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=11300&action=view) tonto-1.0 input file stdin.h.uhf With this attachment as input I get a successful output with tonto-1.0. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26106
[Bug fortran/26106] [meta-bug] Gfortran can't compile tonto
--- Comment #20 from jvdelisle at gcc dot gnu dot org 2006-04-20 06:25 --- Created an attachment (id=11301) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=11301&action=view) tonto-1.0 output for stdin.h.uhf Here is the output from the above patch. When I go to stdin.h2o.blyp I get a segfault. Valgrind is showing unitialized values being used. I am not using the spec version of tonto. I am using the 1.0 download from sourceforge. An added note, when attempting to compile tonto with the -g option I got an ice related to transfer. I will have to take another look later and report back here. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26106
[Bug fortran/27138] gfortran: read(*,*) myInt advances only one character on error
--- Comment #10 from jvdelisle at gcc dot gnu dot org 2006-04-21 03:47 --- Subject: Bug 27138 Author: jvdelisle Date: Fri Apr 21 03:47:23 2006 New Revision: 113131 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=113131 Log: 2006-04-20 Jerry DeLisle <[EMAIL PROTECTED]> PR libgfortran/27138 * io/list_read.c (eat_line): New function. (parse_repeat): Use new function and free_saved. (read_logical): Same. (read_integer): Use new function. (parse_real): Use nml_bad_return and new function. (read_complex): Use new function and free_saved. (read_real): Same. Modified: branches/gcc-4_1-branch/libgfortran/ChangeLog branches/gcc-4_1-branch/libgfortran/io/list_read.c branches/gcc-4_1-branch/libgfortran/io/unit.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27138
[Bug fortran/27138] gfortran: read(*,*) myInt advances only one character on error
--- Comment #11 from jvdelisle at gcc dot gnu dot org 2006-04-21 03:51 --- Subject: Bug 27138 Author: jvdelisle Date: Fri Apr 21 03:51:44 2006 New Revision: 113132 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=113132 Log: 2006-04-20 Jerry DeLisle <[EMAIL PROTECTED]> PR libgfortran/27138 * gfortran.dg/read_bad_advance.f90: New test Added: branches/gcc-4_1-branch/gcc/testsuite/gfortran.dg/read_bad_advance.f90 Modified: branches/gcc-4_1-branch/gcc/testsuite/ChangeLog -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27138
[Bug fortran/27138] gfortran: read(*,*) myInt advances only one character on error
--- Comment #12 from jvdelisle at gcc dot gnu dot org 2006-04-21 03:53 --- Fixed on 4.1 and 4.2. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED Target Milestone|--- |4.1.1 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27138
[Bug target/27253] [4.1/4.2 regression]: Gcc -m64 -m32 passes --32 --64 to assembler
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2006-04-22 01:17 --- Ignore this comment. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27253
[Bug fortran/26106] [meta-bug] Gfortran can't compile tonto
--- Comment #21 from jvdelisle at gcc dot gnu dot org 2006-04-22 04:48 --- I am able to compile with -g OK. Not sure what I was seeing the other night. Here is a backtrace where I see a segfault: (gdb) bt #0 0x082c1c15 in __atom_module__n_bf ([EMAIL PROTECTED]) at f95files/atom.F90:2251 #1 0x082cb859 in __atomvec_module__n_bf ([EMAIL PROTECTED]) at f95files/atomvec.F90:4147 #2 0x081296ae in __mol_module__set_basis_info ([EMAIL PROTECTED]) at f95files/mol.F90:3473 #3 0x0812a519 in __mol_module__resolve_gaussianbasis_info ([EMAIL PROTECTED]) at f95files/mol.F90:3355 #4 0x0812a5e0 in __mol_module__resolve_basis_info ([EMAIL PROTECTED]) at f95files/mol.F90:3290 #5 0x080d5dd6 in __mol_module__read_atoms ([EMAIL PROTECTED]) at f95files/mol.F90:9587 #6 0x0804e79d in __mol_main_module__process_keyword ([EMAIL PROTECTED], [EMAIL PROTECTED], _keyword=128) at f95files/mol_main.F90:3844 #7 0x08050e13 in __mol_main_module__read_keywords ([EMAIL PROTECTED]) at f95files/mol_main.F90:3815 #8 0x08051341 in __mol_main_module__main ([EMAIL PROTECTED]) at f95files/mol_main.F90:3753 #9 0x08049a3c in MAIN__ () at f95files/run_mol.F90:134 #10 0x084a0ef7 in main (argc=Cannot access memory at address 0x3 ) at ../../../main/libgfortran/fmain.c:18 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26106
[Bug libfortran/24459] gfortran namelist problem
-- 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|REOPENED|ASSIGNED Last reconfirmed|2005-10-21 22:27:30 |2006-04-22 23:23:31 date|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24459
[Bug libfortran/20257] Fortran runtime error: End of record occurs when writing large arrays
--- Comment #10 from jvdelisle at gcc dot gnu dot org 2006-04-23 02:05 --- Subject: Bug 20257 Author: jvdelisle Date: Sun Apr 23 02:04:58 2006 New Revision: 113190 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=113190 Log: 2006-04-22 Jerry DeLisle <[EMAIL PROTECTED]> PR libgfortran/20257 * io/io.h: Add prototypes for get_internal_unit and free_internal_unit. * io/unit.c (get_internal_unit): Initialize unit number, not zero. (free_internal_unit): New function to consolidate freeing memory. (get_unit): Initialize internal_unit_desc to NULL when unit is external. * io/unix.c (mem_close): Check for not NULL before freeing memory. * io/transfer.c (read_block): Reset bytes_left and skip error if unit is preconnected and default record length is reached. (read_block_direct): Ditto. (write_block): Ditto. (write_buf): Ditto. (data_transfer_init): Only flush if not internal unit. (finalize_transfer): Ditto and delete code to free memory used by internal units. (st_read_done): Use new function - free_internal_unit. (st_write_done): Use new function - free_internal unit. Modified: trunk/libgfortran/ChangeLog trunk/libgfortran/io/io.h trunk/libgfortran/io/transfer.c trunk/libgfortran/io/unit.c trunk/libgfortran/io/unix.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20257
[Bug driver/27314] ld can't find libgfortran.so.1 on x86-64
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2006-04-26 00:56 --- My experiance has been that if you have gfortran installed from a distribution such as Fedora and you build your own later version of gfortran from source and you do not configure the later version to install in its own place and you do not set LD_LIBRARY_PATH to point to that place, you will get this error. It tries to use the libary from the distribution which is typically 4.0.x and gives that error. Try: export LD_LIBRARY_PATH=/scr_bar/johan/local/lib Also I am not sure about using commas in the compile command to separate things. Maybe use -rpath /scr_bar.johan/local/lib without that comma in between. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27314
[Bug fortran/27304] gfortran: Warn/abort when format in write does not fit passed arguments
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2006-04-26 04:10 --- I am not sure (emphasis on not sure) I agree with this. But I can explain what it is doing. It is correctly printing out the letter 'n' then its looking for the first data item and finds the integer in the list, it reverts on the format statement, performs it and then its done because there are no more data items. At least its logical. :) I wonder if this is a case of illegal code. Intel errors on "infinite format". In other words it keeps reverting looking for a format specifier. gfortran is format driven until there is no more data. g77 exactly matches gfortran in behavior. We should check the standard. Is it required that there is a data format specifier? If not, then this could be an enhancement. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27304
[Bug fortran/27304] gfortran: Warn/abort when format in write does not fit passed arguments
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2006-04-26 22:53 --- The standard reference seems clear. I will see about giving a runtime error. Someone else will have to do the compile time magic. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27304
[Bug fortran/27304] gfortran: Warn/abort when format in write does not fit passed arguments
--- Comment #7 from jvdelisle at gcc dot gnu dot org 2006-04-27 06:02 --- Tobias, I hope this is what you were looking for. I don't really think we need a compile time check. That would be pretty involved to do and the error is caught at runtime. What do you think? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27304
[Bug fortran/27351] -ffixed-line-length-132 ICE on 178.galgel in SPEC CPU 2K
--- Comment #8 from jvdelisle at gcc dot gnu dot org 2006-04-28 22:25 --- Here is valgrind report using allocate_zerosize.f90 as a testcase. This is definitely a memory leak problem: --4718-- supp: 13 dl_relocate_object ==4718== malloc/free: in use at exit: 21254 bytes in 131 blocks. ==4718== malloc/free: 265 allocs, 134 frees, 31979 bytes allocated. ==4718== ==4718== searching for pointers to 131 not-freed blocks. ==4718== checked 65008 bytes. ==4718== ==4718== 4 bytes in 1 blocks are definitely lost in loss record 1 of 8 ==4718==at 0x1B909B71: calloc (vg_replace_malloc.c:175) ==4718==by 0x805EE76: xcalloc (xmalloc.c:162) ==4718==by 0x4AFD7E: __libc_start_main (in /lib/libc-2.3.6.so) ==4718==by 0x80495D0: (within /mnt/sdb2/usr/bin/gfortran) ==4718== ==4718== ==4718== 30 bytes in 1 blocks are definitely lost in loss record 2 of 8 ==4718==at 0x1B909222: malloc (vg_replace_malloc.c:130) ==4718==by 0x805D708: make_relative_prefix (make-relative-prefix.c:361) ==4718==by 0x804D36C: process_command (gcc.c:3370) ==4718==by 0x805345B: main (gcc.c:6182) ==4718== ==4718== ==4718== 5305 (5265 direct, 40 indirect) bytes in 62 blocks are definitely lost in loss record 7 of 8 ==4718==at 0x1B909222: malloc (vg_replace_malloc.c:130) ==4718==by 0x805EEB5: xmalloc (xmalloc.c:147) ==4718== ==4718== LEAK SUMMARY: ==4718==definitely lost: 5299 bytes in 64 blocks. ==4718==indirectly lost: 40 bytes in 3 blocks. ==4718== possibly lost: 0 bytes in 0 blocks. ==4718==still reachable: 15915 bytes in 64 blocks. ==4718== suppressed: 0 bytes in 0 blocks. ==4718== Reachable blocks (those to which a pointer was found) are not shown. ==4718== To see them, rerun with: --show-reachable=yes --4718-- TT/TC: 0 tc sectors discarded. --4718--5019 tt_fast misses. --4718-- translate: new 4985 (80515 -> 1094312; ratio 135:10) --4718--discard 0 (0 -> 0; ratio 0:10). --4718-- chainings: 3496 chainings, 0 unchainings. --4718-- dispatch: 209150 jumps (bb entries); of them 19480 (9%) unchained. --4718--5/5697 major/minor sched events. --4718-- reg-alloc: 1002 t-req-spill, 195192+6670 orig+spill uis, --4718--26176 total-reg-rank --4718--sanity: 6 cheap, 1 expensive checks. --4718--ccalls: 17108 C calls, 56% saves+restores avoided (56636 bytes) --4718--23002 args, avg 0.87 setup instrs each (5660 bytes) --4718--0% clear the stack (51072 bytes) --4718--7446 retvals, 32% of reg-reg movs avoided (4656 bytes) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27351
[Bug c/27354] New: Memory leak in make_relative_prefix
Using valgrind: valgrind -v --leak-check=full gfc -v --snip-- ==4758== 30 bytes in 1 blocks are definitely lost in loss record 1 of 6 ==4758==at 0x1B909222: malloc (vg_replace_malloc.c:130) ==4758==by 0x805D708: make_relative_prefix (make-relative-prefix.c:361) ==4758==by 0x804D36C: process_command (gcc.c:3370) ==4758==by 0x805345B: main (gcc.c:6182) --snip-- -- Summary: Memory leak in make_relative_prefix Product: gcc Version: 4.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jvdelisle at gcc dot gnu dot org GCC host triplet: i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27354
[Bug fortran/27351] -ffixed-line-length-132 ICE on 178.galgel in SPEC CPU 2K
--- Comment #9 from jvdelisle at gcc dot gnu dot org 2006-04-28 22:34 --- I see that one of these leaks has nothing to do with gfortran. So maybe I have not captured anything related to this bug. See PR27354 which I just submitted. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27351
[Bug fortran/27304] gfortran: Warn/abort when format in write does not fit passed arguments
--- Comment #9 from jvdelisle at gcc dot gnu dot org 2006-04-28 23:55 --- Subject: Bug 27304 Author: jvdelisle Date: Fri Apr 28 23:55:30 2006 New Revision: 113363 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=113363 Log: 2006-04-28 Jerry DeLisle <[EMAIL PROTECTED]> PR libgfortran/27304 * io/transfer.c (formatted_transfer_scalar): Generate error if data descriptors are exhausted. * io/format.c (next_format0): Fix comment. Modified: trunk/libgfortran/ChangeLog trunk/libgfortran/io/format.c trunk/libgfortran/io/transfer.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27304
[Bug fortran/27304] gfortran: Warn/abort when format in write does not fit passed arguments
--- Comment #10 from jvdelisle at gcc dot gnu dot org 2006-04-29 00:02 --- Subject: Bug 27304 Author: jvdelisle Date: Sat Apr 29 00:02:10 2006 New Revision: 113364 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=113364 Log: 2006-04-28 Jerry DeLisle <[EMAIL PROTECTED]> PR libgfortran/27304 * gfortran.dg/fmt_exhaust.f90: New test. Added: trunk/gcc/testsuite/gfortran.dg/fmt_exhaust.f90 Modified: trunk/gcc/testsuite/ChangeLog -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27304
[Bug libfortran/20257] Fortran runtime error: End of record occurs when writing large arrays
--- Comment #11 from jvdelisle at gcc dot gnu dot org 2006-04-29 04:27 --- Subject: Bug 20257 Author: jvdelisle Date: Sat Apr 29 04:27:09 2006 New Revision: 113373 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=113373 Log: 2006-04-28 Jerry DeLisle <[EMAIL PROTECTED]> PR libgfortran/20257 * io/io.h: Add prototypes for get_internal_unit and free_internal_unit. * io/unit.c (get_internal_unit): Initialize unit number, not zero. (free_internal_unit): New function to consolidate freeing memory. (get_unit): Initialize internal_unit_desc to NULL when unit is external. * io/unix.c (mem_close): Check for not NULL before freeing memory. * io/transfer.c (read_block): Reset bytes_left and skip error if unit is preconnected and default record length is reached. (read_block_direct): Ditto. (write_block): Ditto. (write_buf): Ditto. (data_transfer_init): Only flush if not internal unit. (finalize_transfer): Ditto and delete code to free memory used by internal units. (st_read_done): Use new function - free_internal_unit. (st_write_done): Use new function - free_internal unit. Modified: branches/gcc-4_1-branch/libgfortran/ChangeLog branches/gcc-4_1-branch/libgfortran/io/io.h branches/gcc-4_1-branch/libgfortran/io/transfer.c branches/gcc-4_1-branch/libgfortran/io/unit.c branches/gcc-4_1-branch/libgfortran/io/unix.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20257
[Bug libfortran/20257] Fortran runtime error: End of record occurs when writing large arrays
--- Comment #12 from jvdelisle at gcc dot gnu dot org 2006-04-29 05:47 --- Fixed on Trunk and now 4.1 branch -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20257
[Bug libfortran/27360] Memory leaks when reading logicals
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2006-04-30 00:12 --- I will look into this. Thought we had them all, but maybe not. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27360
[Bug libfortran/27360] Memory leaks when reading logicals
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2006-04-30 01:15 --- Confirmed and i found the spot in read_logical. I will have a fix shortly. My bad on this one. -- 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|-00-00 00:00:00 |2006-04-30 01:15:06 date|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27360
[Bug libfortran/27360] Memory leaks when reading logicals
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2006-04-30 03:19 --- Subject: Bug 27360 Author: jvdelisle Date: Sun Apr 30 03:19:37 2006 New Revision: 113388 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=113388 Log: 2006-04-29 Jerry DeLisle <[EMAIL PROTECTED]> PR libgfortran/27360 * io/list_read.c (read_logical): Free line_buffer and free saved. Modified: trunk/libgfortran/ChangeLog trunk/libgfortran/io/list_read.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27360
[Bug libfortran/27360] Memory leaks when reading logicals
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2006-04-30 19:53 --- Subject: Bug 27360 Author: jvdelisle Date: Sun Apr 30 19:53:41 2006 New Revision: 113396 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=113396 Log: 2006-04-30 Jerry DeLisle <[EMAIL PROTECTED]> PR libgfortran/27360 * io/list_read.c (read_logical): Free line_buffer and free saved. Modified: branches/gcc-4_1-branch/libgfortran/ChangeLog branches/gcc-4_1-branch/libgfortran/io/list_read.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27360
[Bug libfortran/27360] Memory leaks when reading logicals
--- Comment #7 from jvdelisle at gcc dot gnu dot org 2006-04-30 19:55 --- Fixed on 4.1 and 4.2 -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27360
[Bug fortran/27304] gfortran: Warn/abort when format in write does not fit passed arguments
--- Comment #11 from jvdelisle at gcc dot gnu dot org 2006-04-30 20:59 --- Subject: Bug 27304 Author: jvdelisle Date: Sun Apr 30 20:59:08 2006 New Revision: 113397 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=113397 Log: 2006-04-30 Jerry DeLisle <[EMAIL PROTECTED]> PR libgfortran/27304 * io/transfer.c (formatted_transfer_scalar): Generate error if data descriptors are exhausted. * io/format.c (next_format0): Fix comment. Modified: branches/gcc-4_1-branch/libgfortran/ChangeLog branches/gcc-4_1-branch/libgfortran/io/format.c branches/gcc-4_1-branch/libgfortran/io/transfer.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27304
[Bug fortran/27304] gfortran: Warn/abort when format in write does not fit passed arguments
--- Comment #12 from jvdelisle at gcc dot gnu dot org 2006-04-30 21:02 --- Subject: Bug 27304 Author: jvdelisle Date: Sun Apr 30 21:02:10 2006 New Revision: 113398 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=113398 Log: 2006-04-30 Jerry DeLisle <[EMAIL PROTECTED]> PR libgfortran/27304 * gfortran.dg/fmt_exhaust.f90: New test. Added: branches/gcc-4_1-branch/gcc/testsuite/gfortran.dg/fmt_exhaust.f90 Modified: branches/gcc-4_1-branch/gcc/testsuite/ChangeLog -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27304
[Bug fortran/27304] gfortran: Warn/abort when format in write does not fit passed arguments
--- Comment #13 from jvdelisle at gcc dot gnu dot org 2006-04-30 21:02 --- Fixed on 4.1 and 4.2 -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27304
[Bug libfortran/24459] gfortran namelist problem
--- Comment #13 from jvdelisle at gcc dot gnu dot org 2006-05-02 00:02 --- Patch here: http://gcc.gnu.org/ml/fortran/2006-05/msg0.html Waiting for approval -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24459
[Bug rtl-optimization/17088] poor fortran optimisation at -O2/3
--- Comment #12 from jvdelisle at gcc dot gnu dot org 2006-05-02 05:01 --- With: $ gfc -v Using built-in specs. Target: i686-pc-linux-gnu Configured with: ../main/configure --prefix=/home/jerry/gcc/usr --enable-languages=c,fortran --disable-libmudflap Thread model: posix gcc version 4.2.0 20060424 (experimental) $ gfc -O2 -march=pentium4 test-optimize.f90 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17088
[Bug fortran/27304] gfortran: Warn/abort when format in write does not fit passed arguments
--- Comment #16 from jvdelisle at gcc dot gnu dot org 2006-05-05 00:13 --- I can not reproduce this here. I don't have that platform. I am guessing this is a platform specific problem or a build problem. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27304
[Bug fortran/24993] LAPACK builds but dies in the testsuite
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2006-05-05 05:37 --- I would like to propose we close this bug. LAPACK has been working fine since 4.1. Any objections? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24993
[Bug fortran/21130] 38822 lines of Fortran 90 takes more than 10 minutes to compile on a dual 3GHz P4 Linux box with lots of RAM
--- Comment #13 from jvdelisle at gcc dot gnu dot org 2006-05-05 05:40 --- Bud, unless you are going to chase this further I vote that you close this PR. Was the patch going to go to 4.1 branch as well? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21130
[Bug libfortran/27575] gfortran - does not generate error when trying to read too much data
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2006-05-14 23:46 --- Confirmed. -- 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|-00-00 00:00:00 |2006-05-14 23:46:50 date|| Summary|gfortran - does not generate|gfortran - does not generate |error when trying to read |error when trying to read |too much data |too much data http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27575
[Bug libfortran/27575] gfortran - does not generate error when trying to read too much data
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2006-05-15 06:48 --- Patch is on its way. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27575
[Bug fortran/27634] formatted reading/writing: real format without dot
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2006-05-17 00:16 --- I will investigate this a bit. -- 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|-00-00 00:00:00 |2006-05-17 00:16:35 date|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27634
[Bug libfortran/27575] gfortran - does not generate error when trying to read too much data
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2006-05-17 00:37 --- Subject: Bug 27575 Author: jvdelisle Date: Wed May 17 00:36:53 2006 New Revision: 113837 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=113837 Log: 2006-05-16 Jerry DeLisle <[EMAIL PROTECTED]> PR libgfortran/27575 * io/transfer.c (read_block): Add check for end file condition. (read_block_direct): Add check for end file condition. Modified: trunk/libgfortran/ChangeLog trunk/libgfortran/io/transfer.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27575
[Bug libfortran/27575] gfortran - does not generate error when trying to read too much data
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2006-05-17 00:41 --- Subject: Bug 27575 Author: jvdelisle Date: Wed May 17 00:40:23 2006 New Revision: 113838 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=113838 Log: 2006-05-16 Jerry DeLisle <[EMAIL PROTECTED]> PR libgfortran/27575 * gfortran.dg/read_eof_4.f90: New test. Added: trunk/gcc/testsuite/gfortran.dg/read_eof_4.f90 Modified: trunk/gcc/testsuite/ChangeLog -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27575
[Bug libfortran/27652] Array output does not self wrap
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2006-05-18 03:49 --- [EMAIL PROTECTED] pr27652]$ ./a.out 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 By adjusting my terminal width I can get any number of alignments. This is not a bug or even an enhancement. This is why there are format statements. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||INVALID http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27652
[Bug libfortran/27652] Array output does not self wrap
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2006-05-18 05:10 --- also do something like this: print "(5(f10))", a you will get a new line after every 5 values printed. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27652
[Bug libfortran/27652] Array output does not self wrap
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2006-05-18 05:16 --- Oops, I forgot the period. You need to match the width and precsion you want printed. For complex maybe you want to use 6 or 8 instead of the 5 for repeat count. print "(5(f10.4))", a -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27652
[Bug libfortran/22423] Warnings when building libgfortran
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2006-05-20 02:56 --- I will fix the one in transfer.c as obvious. I don't understand the issue in list_read.c I have a namelist patch pending for that file so if someone could give me a hint I would be happy to fix that as well. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22423
[Bug libfortran/22423] Warnings when building libgfortran
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2006-05-20 03:30 --- Subject: Bug 22423 Author: jvdelisle Date: Sat May 20 03:29:58 2006 New Revision: 113923 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=113923 Log: 2006-05-19 Jerry DeLisle <[EMAIL PROTECTED]> PR libgfortran/22423 * io/transfer.c (read_block): Return NULL instead of nothing. Modified: trunk/libgfortran/ChangeLog trunk/libgfortran/io/transfer.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22423
[Bug libfortran/24459] gfortran namelist problem
--- Comment #16 from jvdelisle at gcc dot gnu dot org 2006-05-20 07:15 --- Subject: Bug 24459 Author: jvdelisle Date: Sat May 20 07:14:50 2006 New Revision: 113924 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=113924 Log: 2006-05-20 Jerry DeLisle <[EMAIL PROTECTED]> PR libgfortran/24459 * io/list_read.c (nml_parse_qualifier): Leave loop spec end value at default value unless -std=f95 or if an array section is specified in namelist input. Warn if -pedantic. * io/io.h (st_parameter_dt): Add expanded_read flag. Modified: trunk/libgfortran/ChangeLog trunk/libgfortran/io/io.h trunk/libgfortran/io/list_read.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24459
[Bug libfortran/24459] [4.1 Only] gfortran namelist problem
--- Comment #17 from jvdelisle at gcc dot gnu dot org 2006-05-20 07:20 --- Fixed on 4.2 -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added Summary|gfortran namelist problem |[4.1 Only] gfortran namelist ||problem http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24459
[Bug libfortran/24459] [4.1 Only] gfortran namelist problem
--- Comment #18 from jvdelisle at gcc dot gnu dot org 2006-05-21 01:56 --- Subject: Bug 24459 Author: jvdelisle Date: Sun May 21 01:56:04 2006 New Revision: 113948 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=113948 Log: 2006-05-20 Jerry DeLisle <[EMAIL PROTECTED]> PR libgfortran/24459 * gfortran.dg/namelist_24.f90: New test. * gfortran.dg/namelist_12.f: Fix typo in comment. Added: trunk/gcc/testsuite/gfortran.dg/namelist_24.f90 Modified: trunk/gcc/testsuite/ChangeLog trunk/gcc/testsuite/gfortran.dg/namelist_12.f -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24459
[Bug libfortran/27704] New: Incorrect runtime error on multiple OPEN
The following should not produce a runtime error.
OPEN(8, FORM = 'unformatted', STATUS = 'scratch')
OPEN(8, FORM = 'unformatted', STATUS = 'scratch')
end
There may be other combinations of arguments to open that should not error,
See the following thread:
http://gcc.gnu.org/ml/fortran/2006-05/msg00307.html
--
Summary: Incorrect runtime error on multiple OPEN
Product: gcc
Version: 4.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libfortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: jvdelisle at gcc dot gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27704
[Bug fortran/27683] Many new GFORTRAN testsuite failures
--- Comment #7 from jvdelisle at gcc dot gnu dot org 2006-05-24 13:48 --- Look in Changelog and you will see the most recent two in trunk have not gone to 4.1 yet. The namelist patch for expanded reads does touch io.h The other was a simple problem. I changed a return; to return NULL; to get rid of a warning. That leaves the namelist patch. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27683
[Bug fortran/27683] Many new GFORTRAN testsuite failures
--- Comment #9 from jvdelisle at gcc dot gnu dot org 2006-05-25 00:40 --- Dale, I believe this is the correct use of update to get back to previous versions if gcc is your main trunk directory and you were one directory above when you invoked the command. You may want to check in libgfortran/io/io.h and make sure there is no variable called expanded_read. If you were in the main top level directory, svn -r 113923 is sufficient, otherwise you may get the gcc subdirectory only that does not contain libgfortran So, assuming you got there correctly, this rules out any of my patches. Please let me know if you can confirm. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27683
[Bug fortran/27757] Problems with direct access io
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2006-05-25 00:51 --- I will take a look at this one. This does seem odd. Can you tell us what platform you are running on and what version of gfortran. gfortran -v will tell us useful info. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27757
[Bug fortran/27757] Problems with direct access io
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2006-05-25 01:20 --- If you are running a gfortran straight from the FC 4 distribution it probably does not have the latest fixes to the IO that we have in the 4.1 branch. These have not been released yet. Release 4.1.1 is being prepared now. If you are up to it you could grab a gcc snapshot and build a 4.1.1 or 4.2 version and try it. 4.2 may not be very stable at the moment so a 4.1 snapshot latest would be a good bet. Let me know what you think and we will keep trying to help you with this. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27757
[Bug fortran/27757] Problems with direct access io
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2006-05-25 05:08 --- http://gcc.gnu.org/mirrors.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27757
[Bug fortran/27683] Many new GFORTRAN testsuite failures
--- Comment #13 from jvdelisle at gcc dot gnu dot org 2006-05-25 14:44 --- Maybe go back farther than the email I just posted to gfortran list suggests. I am suspicious that this is not a gfortran problem, but then 4.1 is working. Take a shot at an April 1 version maybe. You can find the version numbers if you look on some of the testresults mailing list archives. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27683
[Bug fortran/27683] Many new GFORTRAN testsuite failures
--- Comment #18 from jvdelisle at gcc dot gnu dot org 2006-05-26 00:08 --- All of the IO patches for both revs, before and after the failures, exist in 4.1 and 4.2. 4.1 is not failing, so this leads me to believe this is not a libgfortran failure. There is an alignment patch that went in on 4/18/06 with no associated PR. Perhaps this is it, but it is also in 4.1 and 4.2. It is I/O related, but on the frontend side. http://gcc.gnu.org/ml/gcc-patches/2006-04/msg00633.html This patch is beyond my current understanding, so someone else needs to look at it. Andrew? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27683
[Bug fortran/27757] Problems with direct access io
--- Comment #7 from jvdelisle at gcc dot gnu dot org 2006-05-27 02:35 --- The following patch causes no regressions. I can't reproduce the problem here, but I have a hunch. Ray, can you try this and see if it resolves the problem? Thanks for tests and reports. Index: io/transfer.c === *** io/transfer.c (revision 114105) --- io/transfer.c (working copy) *** st_write_done (st_parameter_dt *dtp) *** 2416,2421 --- 2416,2425 break; } + if (dtp->u.p.current_unit != NULL + && dtp->u.p.current_unit->flags.access == ACCESS_DIRECT) + flush (dtp->u.p.current_unit->s); + free_format_data (dtp); free_ionml (dtp); if (dtp->u.p.scratch != NULL) -- 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|-00-00 00:00:00 |2006-05-27 02:35:03 date|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27757
[Bug fortran/27757] Problems with direct access io
--- Comment #8 from jvdelisle at gcc dot gnu dot org 2006-05-27 05:10 --- Here is some good news. I came up with a test case that fails with gfortran and passes with intel. The bad news is that I have not fixed it yet. At least I have something to work with now and its ugly. program testdirect implicit none integer, dimension(100) :: a integer :: i,j,k,ier real:: x a = 0 call random_seed() open(unit=15,file="testdirectio",access="direct",form="unformatted",recl=4) do i=1,100 call random_number(x) k= int(x * 100)+1 a(i)=k write(unit=15, rec=k) k enddo do j=1,100 read(unit=15, rec=a(j), iostat=ier) k if (ier.ne.0) then print *, "No Record: ", j else print *, "Bad Record at ",a(j), k endif enddo close(unit=15, status="delete") end program testdirect -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27757
[Bug fortran/27757] [4.1/4.2 Regression] Problems with direct access io
--- Comment #12 from jvdelisle at gcc dot gnu dot org 2006-05-28 00:40 --- I am confirming this is a regression. The test program works fine on 4.0.2 -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added Summary|Problems with direct access |[4.1/4.2 Regression] |io |Problems with direct access ||io http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27757
[Bug libfortran/24459] [4.1 Only] gfortran namelist problem
--- Comment #19 from jvdelisle at gcc dot gnu dot org 2006-05-29 05:19 --- Subject: Bug 24459 Author: jvdelisle Date: Mon May 29 05:18:58 2006 New Revision: 114182 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=114182 Log: 2006-05-28 Jerry DeLisle <[EMAIL PROTECTED]> PR libgfortran/24459 * io/list_read.c (nml_parse_qualifier): Leave loop spec end value at default value unless -std=f95 or if an array section is specified in namelist input. Warn if -pedantic. * io/io.h (st_parameter_dt): Add expanded_read flag. Modified: branches/gcc-4_1-branch/libgfortran/ChangeLog branches/gcc-4_1-branch/libgfortran/io/io.h branches/gcc-4_1-branch/libgfortran/io/list_read.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24459
[Bug libfortran/24459] [4.1 Only] gfortran namelist problem
--- Comment #20 from jvdelisle at gcc dot gnu dot org 2006-05-29 05:22 --- Subject: Bug 24459 Author: jvdelisle Date: Mon May 29 05:22:05 2006 New Revision: 114184 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=114184 Log: 2006-05-28 Jerry DeLisle <[EMAIL PROTECTED]> PR libgfortran/24459 * gfortran.dg/namelist_24.f90: New test. Added: branches/gcc-4_1-branch/gcc/testsuite/gfortran.dg/namelist_24.f90 Modified: branches/gcc-4_1-branch/gcc/testsuite/ChangeLog -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24459
[Bug libfortran/24459] [4.1 Only] gfortran namelist problem
--- Comment #21 from jvdelisle at gcc dot gnu dot org 2006-05-29 05:23 --- Fixed now on 4.1 -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24459
[Bug fortran/27634] formatted reading/writing: real format without dot
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2006-05-29 19:29 --- Subject: Bug 27634 Author: jvdelisle Date: Mon May 29 19:28:48 2006 New Revision: 114212 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=114212 Log: 2006-05-29 Jerry DeLisle <[EMAIL PROTECTED]> PR libgfortran/27634 * io/format.c (parse_format_list): Allow missing period in format only if -std=legacy. Modified: trunk/libgfortran/ChangeLog trunk/libgfortran/io/format.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27634
[Bug fortran/27634] formatted reading/writing: real format without dot
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2006-05-29 19:34 --- Subject: Bug 27634 Author: jvdelisle Date: Mon May 29 19:33:43 2006 New Revision: 114213 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=114213 Log: 2006-05-29 Jerry DeLisle <[EMAIL PROTECTED]> PR fortran/27634 * io.c (check_format): Add error for missing period in format specifier unless -std=legacy. * gfortran.texi: Add description of expanded namelist read and missing period in format extensions. Modified: trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/gfortran.texi trunk/gcc/fortran/io.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27634
[Bug fortran/27634] formatted reading/writing: real format without dot
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2006-05-29 19:39 --- Subject: Bug 27634 Author: jvdelisle Date: Mon May 29 19:39:15 2006 New Revision: 114214 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=114214 Log: 2006-05-29 Jerry DeLisle <[EMAIL PROTECTED]> PR libgfortran/27634 * gfortran.dg/fmt_missing_period_1.f: New test. * gfortran.dg/fmt_missing_period_2.f: New test. * gfortran.dg/fmt_missing_period_3.f: New test. Added: trunk/gcc/testsuite/gfortran.dg/fmt_missing_period_1.f trunk/gcc/testsuite/gfortran.dg/fmt_missing_period_2.f trunk/gcc/testsuite/gfortran.dg/fmt_missing_period_3.f Modified: trunk/gcc/testsuite/ChangeLog -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27634
[Bug fortran/27634] formatted reading/writing: real format without dot
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2006-05-29 19:42 --- Fixed on 4.2 only. Will not go to 4.1 -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27634
[Bug fortran/27634] formatted reading/writing: real format without dot
-- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added Target Milestone|--- |4.2.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27634
[Bug libfortran/27757] [4.1/4.2 Regression] Problems with direct access io
--- Comment #14 from jvdelisle at gcc dot gnu dot org 2006-05-29 20:49 --- Here is the fix folks. Unbelievable! Index: io/unix.c === *** io/unix.c (revision 114207) --- io/unix.c (working copy) *** fd_seek (unix_stream * s, gfc_offset off *** 569,574 --- 569,575 } s->physical_offset = s->logical_offset = offset; + s->active = 0; return (lseek (s->fd, offset, SEEK_SET) < 0) ? FAILURE : SUCCESS; } -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27757
[Bug libfortran/27757] [4.1/4.2 Regression] Problems with direct access io
--- Comment #15 from jvdelisle at gcc dot gnu dot org 2006-05-29 23:40 --- Subject: Bug 27757 Author: jvdelisle Date: Mon May 29 23:39:53 2006 New Revision: 114220 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=114220 Log: 2006-05-29 Jerry DeLisle <[EMAIL PROTECTED]> PR libgfortran/27757 * io/unix.c (fd_seek): Set active to zero. Modified: trunk/libgfortran/ChangeLog trunk/libgfortran/io/unix.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27757
[Bug libfortran/27757] [4.1/4.2 Regression] Problems with direct access io
--- Comment #16 from jvdelisle at gcc dot gnu dot org 2006-05-29 23:43 --- Subject: Bug 27757 Author: jvdelisle Date: Mon May 29 23:42:55 2006 New Revision: 114221 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=114221 Log: 2006-05-29 Jerry DeLisle <[EMAIL PROTECTED]> PR libgfortran/27757 * gfortran.dg/direct_io_5.f90: New test. Added: trunk/gcc/testsuite/gfortran.dg/direct_io_5.f90 Modified: trunk/gcc/testsuite/ChangeLog -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27757
[Bug libfortran/27757] [4.1/4.2 Regression] Problems with direct access io
--- Comment #17 from jvdelisle at gcc dot gnu dot org 2006-05-30 02:51 --- Subject: Bug 27757 Author: jvdelisle Date: Tue May 30 02:51:26 2006 New Revision: 114227 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=114227 Log: 2006-05-29 Jerry DeLisle <[EMAIL PROTECTED]> PR libgfortran/27757 * io/unix.c (fd_seek): Set active to zero. Modified: branches/gcc-4_1-branch/libgfortran/ChangeLog branches/gcc-4_1-branch/libgfortran/io/unix.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27757
[Bug libfortran/27757] [4.1/4.2 Regression] Problems with direct access io
--- Comment #18 from jvdelisle at gcc dot gnu dot org 2006-05-30 02:54 --- Subject: Bug 27757 Author: jvdelisle Date: Tue May 30 02:54:29 2006 New Revision: 114228 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=114228 Log: 2006-05-29 Jerry DeLisle <[EMAIL PROTECTED]> PR libgfortran/27757 * gfortran.dg/direct_io_5.f90: New test. Added: branches/gcc-4_1-branch/gcc/testsuite/gfortran.dg/direct_io_5.f90 Modified: branches/gcc-4_1-branch/gcc/testsuite/ChangeLog -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27757
[Bug fortran/24993] LAPACK builds but dies in the testsuite
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2006-05-30 04:04 --- No onjections. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added Status|WAITING |RESOLVED Resolution||WORKSFORME http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24993
[Bug libfortran/27575] gfortran - does not generate error when trying to read too much data
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2006-05-30 04:44 --- If someone wants this fix in 4.1, let me know, otherwise I will close this bug shortly. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27575
[Bug libfortran/27757] [4.1/4.2 Regression] Problems with direct access io
--- Comment #19 from jvdelisle at gcc dot gnu dot org 2006-05-30 23:02 --- Fixed on 4.1 and 4.1. Ray also confirmed by separate email that the original application problem is fixed as well. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27757
