[Bug libfortran/26890] SIZE parameter interacts with same variable in IO list character length specification.

2006-04-08 Thread jvdelisle at gcc dot gnu dot org
-- 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

[Bug libfortran/27107] New: Make dependency on io/io.h broken

2006-04-10 Thread jvdelisle at gcc dot gnu dot org
oduct: 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://g

[Bug fortran/27112] Rejects to call a generic procedure by argument keywords.

2006-04-10 Thread jvdelisle at gcc dot gnu dot org
--- 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

[Bug fortran/27112] Rejects to call a generic procedure by argument keywords.

2006-04-11 Thread jvdelisle at gcc dot gnu dot org
--- 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

[Bug fortran/27112] Rejects to call a generic procedure by argument keywords.

2006-04-11 Thread jvdelisle at gcc dot gnu dot org
--- 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 th

[Bug fortran/27138] gfortran: read(*,*) myInt advances only one character on error

2006-04-12 Thread jvdelisle at gcc dot gnu dot org
--- 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

[Bug fortran/27138] gfortran: read(*,*) myInt advances only one character on error

2006-04-12 Thread jvdelisle at gcc dot gnu dot org
--- 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

[Bug fortran/26766] [F2003] Recursive I/O still (again) broken

2006-04-12 Thread jvdelisle at gcc dot gnu dot org
--- 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 <[EMAI

[Bug fortran/26766] [F2003] Recursive I/O still (again) broken

2006-04-12 Thread jvdelisle at gcc dot gnu dot org
--- 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 <[EMAI

[Bug fortran/27138] gfortran: read(*,*) myInt advances only one character on error

2006-04-13 Thread jvdelisle at gcc dot gnu dot org
--- 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

[Bug fortran/27112] Rejects to call a generic procedure by argument keywords.

2006-04-13 Thread jvdelisle at gcc dot gnu dot org
--- 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

[Bug libfortran/26890] SIZE parameter interacts with same variable in IO list character length specification.

2006-04-13 Thread jvdelisle at gcc dot gnu dot org
--- 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 <[EMAI

[Bug target/26980] g++.old-deja/g++.other/init5.C execution test fails

2006-04-13 Thread jvdelisle at gcc dot gnu dot org
--- 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 <[EMAI

[Bug libfortran/26890] SIZE parameter interacts with same variable in IO list character length specification.

2006-04-13 Thread jvdelisle at gcc dot gnu dot org
--- 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

[Bug libfortran/26890] SIZE parameter interacts with same variable in IO list character length specification.

2006-04-13 Thread jvdelisle at gcc dot gnu dot org
--- 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

[Bug fortran/27138] gfortran: read(*,*) myInt advances only one character on error

2006-04-13 Thread jvdelisle at gcc dot gnu dot org
--- 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 cas

[Bug testsuite/25336] Identical tests: gfortran.dg/g77/20030115-1.f gfortran.dg/g77/pr9258.f

2006-04-14 Thread jvdelisle at gcc dot gnu dot org
--- 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 <[EMAI

[Bug testsuite/25336] Identical tests: gfortran.dg/g77/20030115-1.f gfortran.dg/g77/pr9258.f

2006-04-14 Thread jvdelisle at gcc dot gnu dot org
--- 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

[Bug libfortran/20257] Fortran runtime error: End of record occurs when writing large arrays

2006-04-15 Thread jvdelisle at gcc dot gnu dot org
--- 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

[Bug fortran/27138] gfortran: read(*,*) myInt advances only one character on error

2006-04-16 Thread jvdelisle at gcc dot gnu dot org
--- 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 <[EMAI

[Bug fortran/27138] gfortran: read(*,*) myInt advances only one character on error

2006-04-16 Thread jvdelisle at gcc dot gnu dot org
--- 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 <[EMAI

[Bug fortran/26766] [F2003] Recursive I/O still (again) broken

2006-04-16 Thread jvdelisle at gcc dot gnu dot org
--- 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 <[EMAI

[Bug fortran/26766] [F2003] Recursive I/O still (again) broken

2006-04-16 Thread jvdelisle at gcc dot gnu dot org
--- 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 <[EMAI

[Bug fortran/26766] [F2003] Recursive I/O still (again) broken

2006-04-16 Thread jvdelisle at gcc dot gnu dot org
--- 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

[Bug c/27191] New: ice on bootstrap - dwarf2out.c

2006-04-17 Thread jvdelisle at gcc dot gnu dot org
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

2006-04-17 Thread jvdelisle at gcc dot gnu dot org
--- 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

[Bug debug/27188] [4.2 Regression] libgcc2.c:382: internal compiler error: in prune_unused_types_update_strings, at dwarf2out.c:14009

2006-04-17 Thread jvdelisle at gcc dot gnu dot org
--- 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

[Bug fortran/26106] [meta-bug] Gfortran can't compile tonto

2006-04-19 Thread jvdelisle at gcc dot gnu dot org
--- 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 to

[Bug fortran/26106] [meta-bug] Gfortran can't compile tonto

2006-04-19 Thread jvdelisle at gcc dot gnu dot org
--- 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

[Bug fortran/27138] gfortran: read(*,*) myInt advances only one character on error

2006-04-20 Thread jvdelisle at gcc dot gnu dot org
--- 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 <[EMAI

[Bug fortran/27138] gfortran: read(*,*) myInt advances only one character on error

2006-04-20 Thread jvdelisle at gcc dot gnu dot org
--- 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 <[EMAI

[Bug fortran/27138] gfortran: read(*,*) myInt advances only one character on error

2006-04-20 Thread jvdelisle at gcc dot gnu dot org
--- 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

[Bug target/27253] [4.1/4.2 regression]: Gcc -m64 -m32 passes --32 --64 to assembler

2006-04-21 Thread jvdelisle at gcc dot gnu dot org
--- 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

2006-04-21 Thread jvdelisle at gcc dot gnu dot org
--- 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

[Bug libfortran/24459] gfortran namelist problem

2006-04-22 Thread jvdelisle at gcc dot gnu dot org
-- 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

[Bug libfortran/20257] Fortran runtime error: End of record occurs when writing large arrays

2006-04-22 Thread jvdelisle at gcc dot gnu dot org
--- 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 <[EMAI

[Bug driver/27314] ld can't find libgfortran.so.1 on x86-64

2006-04-25 Thread jvdelisle at gcc dot gnu dot org
--- 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

[Bug fortran/27304] gfortran: Warn/abort when format in write does not fit passed arguments

2006-04-25 Thread jvdelisle at gcc dot gnu dot org
--- 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 i

[Bug fortran/27304] gfortran: Warn/abort when format in write does not fit passed arguments

2006-04-26 Thread jvdelisle at gcc dot gnu dot org
--- 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

2006-04-26 Thread jvdelisle at gcc dot gnu dot org
--- 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? --

[Bug fortran/27351] -ffixed-line-length-132 ICE on 178.galgel in SPEC CPU 2K

2006-04-28 Thread jvdelisle at gcc dot gnu dot org
--- 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

[Bug c/27354] New: Memory leak in make_relative_prefix

2006-04-28 Thread jvdelisle at gcc dot gnu dot org
: 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

2006-04-28 Thread jvdelisle at gcc dot gnu dot org
--- 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

[Bug fortran/27304] gfortran: Warn/abort when format in write does not fit passed arguments

2006-04-28 Thread jvdelisle at gcc dot gnu dot org
--- 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 <[EMAI

[Bug fortran/27304] gfortran: Warn/abort when format in write does not fit passed arguments

2006-04-28 Thread jvdelisle at gcc dot gnu dot org
--- 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 <[EMAI

[Bug libfortran/20257] Fortran runtime error: End of record occurs when writing large arrays

2006-04-28 Thread jvdelisle at gcc dot gnu dot org
--- 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 <[EMAI

[Bug libfortran/20257] Fortran runtime error: End of record occurs when writing large arrays

2006-04-28 Thread jvdelisle at gcc dot gnu dot org
--- 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

[Bug libfortran/27360] Memory leaks when reading logicals

2006-04-29 Thread jvdelisle at gcc dot gnu dot org
--- 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

2006-04-29 Thread jvdelisle at gcc dot gnu dot org
--- 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

[Bug libfortran/27360] Memory leaks when reading logicals

2006-04-29 Thread jvdelisle at gcc dot gnu dot org
--- 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 <[EMAI

[Bug libfortran/27360] Memory leaks when reading logicals

2006-04-30 Thread jvdelisle at gcc dot gnu dot org
--- 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 <[EMAI

[Bug libfortran/27360] Memory leaks when reading logicals

2006-04-30 Thread jvdelisle at gcc dot gnu dot org
--- 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

[Bug fortran/27304] gfortran: Warn/abort when format in write does not fit passed arguments

2006-04-30 Thread jvdelisle at gcc dot gnu dot org
--- 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 <[EMAI

[Bug fortran/27304] gfortran: Warn/abort when format in write does not fit passed arguments

2006-04-30 Thread jvdelisle at gcc dot gnu dot org
--- 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 <[EMAI

[Bug fortran/27304] gfortran: Warn/abort when format in write does not fit passed arguments

2006-04-30 Thread jvdelisle at gcc dot gnu dot org
--- 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

[Bug libfortran/24459] gfortran namelist problem

2006-05-01 Thread jvdelisle at gcc dot gnu dot org
--- 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

2006-05-01 Thread jvdelisle at gcc dot gnu dot org
--- 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

[Bug fortran/27304] gfortran: Warn/abort when format in write does not fit passed arguments

2006-05-04 Thread jvdelisle at gcc dot gnu dot org
--- 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

2006-05-04 Thread jvdelisle at gcc dot gnu dot org
--- 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

2006-05-04 Thread jvdelisle at gcc dot gnu dot org
--- 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

2006-05-14 Thread jvdelisle at gcc dot gnu dot org
--- 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

[Bug libfortran/27575] gfortran - does not generate error when trying to read too much data

2006-05-14 Thread jvdelisle at gcc dot gnu dot org
--- 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

2006-05-16 Thread jvdelisle at gcc dot gnu dot org
--- 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

[Bug libfortran/27575] gfortran - does not generate error when trying to read too much data

2006-05-16 Thread jvdelisle at gcc dot gnu dot org
--- 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 <[EMAI

[Bug libfortran/27575] gfortran - does not generate error when trying to read too much data

2006-05-16 Thread jvdelisle at gcc dot gnu dot org
--- 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 <[EMAI

[Bug libfortran/27652] Array output does not self wrap

2006-05-17 Thread jvdelisle at gcc dot gnu dot org
--- 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

[Bug libfortran/27652] Array output does not self wrap

2006-05-17 Thread jvdelisle at gcc dot gnu dot org
--- 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

2006-05-17 Thread jvdelisle at gcc dot gnu dot org
--- 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

[Bug libfortran/22423] Warnings when building libgfortran

2006-05-19 Thread jvdelisle at gcc dot gnu dot org
--- 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

[Bug libfortran/22423] Warnings when building libgfortran

2006-05-19 Thread jvdelisle at gcc dot gnu dot org
--- 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 <[EMAI

[Bug libfortran/24459] gfortran namelist problem

2006-05-20 Thread jvdelisle at gcc dot gnu dot org
--- 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 <[EMAI

[Bug libfortran/24459] [4.1 Only] gfortran namelist problem

2006-05-20 Thread jvdelisle at gcc dot gnu dot org
--- 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

[Bug libfortran/24459] [4.1 Only] gfortran namelist problem

2006-05-20 Thread jvdelisle at gcc dot gnu dot org
--- 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 <[EMAI

[Bug libfortran/27704] New: Incorrect runtime error on multiple OPEN

2006-05-21 Thread jvdelisle at gcc dot gnu dot org
ortran 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

2006-05-24 Thread jvdelisle at gcc dot gnu dot org
--- 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

[Bug fortran/27683] Many new GFORTRAN testsuite failures

2006-05-24 Thread jvdelisle at gcc dot gnu dot org
--- 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

[Bug fortran/27757] Problems with direct access io

2006-05-24 Thread jvdelisle at gcc dot gnu dot org
--- 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

[Bug fortran/27757] Problems with direct access io

2006-05-24 Thread jvdelisle at gcc dot gnu dot org
--- 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

[Bug fortran/27757] Problems with direct access io

2006-05-24 Thread jvdelisle at gcc dot gnu dot org
--- 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

2006-05-25 Thread jvdelisle at gcc dot gnu dot org
--- 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

[Bug fortran/27683] Many new GFORTRAN testsuite failures

2006-05-25 Thread jvdelisle at gcc dot gnu dot org
--- 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

[Bug fortran/27757] Problems with direct access io

2006-05-26 Thread jvdelisle at gcc dot gnu dot org
--- 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/trans

[Bug fortran/27757] Problems with direct access io

2006-05-26 Thread jvdelisle at gcc dot gnu dot org
--- 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

[Bug fortran/27757] [4.1/4.2 Regression] Problems with direct access io

2006-05-27 Thread jvdelisle at gcc dot gnu dot org
--- 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

[Bug libfortran/24459] [4.1 Only] gfortran namelist problem

2006-05-28 Thread jvdelisle at gcc dot gnu dot org
--- 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 <[EMAI

[Bug libfortran/24459] [4.1 Only] gfortran namelist problem

2006-05-28 Thread jvdelisle at gcc dot gnu dot org
--- 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 <[EMAI

[Bug libfortran/24459] [4.1 Only] gfortran namelist problem

2006-05-28 Thread jvdelisle at gcc dot gnu dot org
--- 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

[Bug fortran/27634] formatted reading/writing: real format without dot

2006-05-29 Thread jvdelisle at gcc dot gnu dot org
--- 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 <[EMAI

[Bug fortran/27634] formatted reading/writing: real format without dot

2006-05-29 Thread jvdelisle at gcc dot gnu dot org
--- 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 <[EMAI

[Bug fortran/27634] formatted reading/writing: real format without dot

2006-05-29 Thread jvdelisle at gcc dot gnu dot org
--- 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 <[EMAI

[Bug fortran/27634] formatted reading/writing: real format without dot

2006-05-29 Thread jvdelisle at gcc dot gnu dot org
--- 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

[Bug fortran/27634] formatted reading/writing: real format without dot

2006-05-29 Thread jvdelisle at gcc dot gnu dot org
-- 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

2006-05-29 Thread jvdelisle at gcc dot gnu dot org
--- 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

[Bug libfortran/27757] [4.1/4.2 Regression] Problems with direct access io

2006-05-29 Thread jvdelisle at gcc dot gnu dot org
--- 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 <[EMAI

[Bug libfortran/27757] [4.1/4.2 Regression] Problems with direct access io

2006-05-29 Thread jvdelisle at gcc dot gnu dot org
--- 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 <[EMAI

[Bug libfortran/27757] [4.1/4.2 Regression] Problems with direct access io

2006-05-29 Thread jvdelisle at gcc dot gnu dot org
--- 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 <[EMAI

[Bug libfortran/27757] [4.1/4.2 Regression] Problems with direct access io

2006-05-29 Thread jvdelisle at gcc dot gnu dot org
--- 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 <[EMAI

[Bug fortran/24993] LAPACK builds but dies in the testsuite

2006-05-29 Thread jvdelisle at gcc dot gnu dot org
--- 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

[Bug libfortran/27575] gfortran - does not generate error when trying to read too much data

2006-05-29 Thread jvdelisle at gcc dot gnu dot org
--- 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

2006-05-30 Thread jvdelisle at gcc dot gnu dot org
--- 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

  1   2   3   4   5   6   7   8   9   10   >