[Bug libfortran/24794] problem with namelist input of character array

2005-11-19 Thread jvdelisle at gcc dot gnu dot org
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2005-11-19 20:43 --- I have the patch for this working and will be submitting to the list for approval soon. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24794

[Bug libfortran/24794] problem with namelist input of character array

2005-11-19 Thread jvdelisle at gcc dot gnu dot org
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2005-11-20 02:00 --- Patch submitted for review and approval. Christoph, thankyou for submitting this PR and the example case. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24794

[Bug libfortran/24794] problem with namelist input of character array

2005-11-22 Thread jvdelisle at gcc dot gnu dot org
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2005-11-23 02:02 --- Subject: Bug 24794 Author: jvdelisle Date: Wed Nov 23 02:02:31 2005 New Revision: 107394 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=107394 Log: 2005-11-22 Jerry DeLisle <[EMAI

[Bug libfortran/24794] problem with namelist input of character array

2005-11-22 Thread jvdelisle at gcc dot gnu dot org
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2005-11-23 02:14 --- Subject: Bug 24794 Author: jvdelisle Date: Wed Nov 23 02:14:26 2005 New Revision: 107396 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=107396 Log: 2005-11-22 Jerry DeLisle <[EMAI

[Bug libfortran/24794] problem with namelist input of character array

2005-11-22 Thread jvdelisle at gcc dot gnu dot org
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2005-11-23 02:28 --- Subject: Bug 24794 Author: jvdelisle Date: Wed Nov 23 02:28:44 2005 New Revision: 107397 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=107397 Log: 2005-11-22 Jerry DeLisle <[EMAI

[Bug libfortran/24794] problem with namelist input of character array

2005-11-22 Thread jvdelisle at gcc dot gnu dot org
--- Comment #7 from jvdelisle at gcc dot gnu dot org 2005-11-23 02:30 --- Subject: Bug 24794 Author: jvdelisle Date: Wed Nov 23 02:30:23 2005 New Revision: 107399 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=107399 Log: 2005-11-22 Jerry DeLisle <[EMAI

[Bug libfortran/24794] problem with namelist input of character array

2005-11-23 Thread jvdelisle at gcc dot gnu dot org
--- Comment #8 from jvdelisle at gcc dot gnu dot org 2005-11-23 20:57 --- Fixed in 4.1 and 4.2 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24794

[Bug libfortran/24794] problem with namelist input of character array

2005-11-23 Thread jvdelisle at gcc dot gnu dot org
--- Comment #9 from jvdelisle at gcc dot gnu dot org 2005-11-24 00:49 --- Fixed in 4.1 and 4.2, if someone has a dieing need for this in 4.0 let me know and I will commit the fix there as well. -- jvdelisle at gcc dot gnu dot org changed: What|Removed

[Bug libfortran/24459] gfortran namelist problem

2005-11-23 Thread jvdelisle at gcc dot gnu dot org
--- Comment #7 from jvdelisle at gcc dot gnu dot org 2005-11-24 07:21 --- This is not a bug. Gfortran is complying with F95 namelist read requirements. This would be an enhancement or extension. The work around is to use correct array triplets in the array qualifiers for namelist

[Bug libfortran/24459] gfortran namelist problem

2005-11-24 Thread jvdelisle at gcc dot gnu dot org
--- Comment #9 from jvdelisle at gcc dot gnu dot org 2005-11-24 17:25 --- After going to comp.lang.fortran I determined this is not a bug and gfortran is correctly handling the given namelist. To get desired behavior use array qualifiers with array triplet notation. -- jvdelisle

[Bug libfortran/24459] gfortran namelist problem

2005-11-25 Thread jvdelisle at gcc dot gnu dot org
--- Comment #10 from jvdelisle at gcc dot gnu dot org 2005-11-25 19:44 --- I am reopening this PR because I recieved information that the behavior is a pre F90 feature commonly used before array triplet notation was introduced. I also found that it is supported in g77. So we

[Bug libfortran/25039] broken formatted I/O

2005-11-25 Thread jvdelisle at gcc dot gnu dot org
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2005-11-25 22:00 --- Confirmed on 4.2 -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug libfortran/25039] broken formatted I/O

2005-11-25 Thread jvdelisle at gcc dot gnu dot org
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2005-11-26 01:35 --- -fdump-tree-original: See below. What is this unprintable character? Is that right? MAIN__ () { int4 i2; int4 i1; { struct __st_parameter_dtquireY dt_parm.0; dt_parm.0.common.filename

[Bug libfortran/25039] broken formatted I/O

2005-11-26 Thread jvdelisle at gcc dot gnu dot org
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2005-11-26 19:10 --- The problem with the test case is not related to the weird dump I am getting. Notice I also have a 'Y' in there too as well as a '\b' character. This is really weird. I also noticed some

[Bug fortran/25109] formatted reads with embedded blanks in input fields

2005-11-26 Thread jvdelisle at gcc dot gnu dot org
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2005-11-26 23:53 --- Please attach an actual example of the code so we can study it. This is probably a duplicate of pr25039, but I need to see an example to confirm. -- jvdelisle at gcc dot gnu dot org changed: What

[Bug fortran/25109] formatted reads with embedded blanks in input fields

2005-11-26 Thread jvdelisle at gcc dot gnu dot org
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2005-11-27 00:34 --- Confirmed, we are deafaulting BLANK = to UNSPECIFIED rather than NULL as required by F95 Standard. Regression testing a patch now. -- jvdelisle at gcc dot gnu dot org changed: What|Removed

[Bug fortran/25109] formatted reads with embedded blanks in input fields

2005-11-27 Thread jvdelisle at gcc dot gnu dot org
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2005-11-28 00:23 --- Subject: Bug 25109 Author: jvdelisle Date: Mon Nov 28 00:23:28 2005 New Revision: 107588 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=107588 Log: 2005-11-27 Jerry DeLisle <[EMAI

[Bug libfortran/25139] Fortran runtime error: Invalid argument

2005-11-28 Thread jvdelisle at gcc dot gnu dot org
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2005-11-29 02:16 --- Reduced test case: program test dimension data(100) read(11,end=1000 )data 1000 continue backspace 11 backspace 11 end I will have to check to see if this is

[Bug libfortran/25039] broken formatted I/O

2005-11-28 Thread jvdelisle at gcc dot gnu dot org
--- Comment #9 from jvdelisle at gcc dot gnu dot org 2005-11-29 02:28 --- Yes, I have a patch under review right now that fixes this. However, I am going to add a requirement that -std=legacy or similar be invoked, otherwise we would be non-compliant with F95 Standard which disallows

[Bug libfortran/25039] broken formatted I/O

2005-11-28 Thread jvdelisle at gcc dot gnu dot org
--- Comment #10 from jvdelisle at gcc dot gnu dot org 2005-11-29 03:50 --- Dang, I just noticed that Iwan had proposed a patch in comment #5 so I did my own. My apologies please. Does Iwan have copyright assignment in place? I took a different approach with my patch because I did

[Bug fortran/25149] New: Compiler dies on -std=f95

2005-11-28 Thread jvdelisle at gcc dot gnu dot org
: gcc Version: 4.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran 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=25149

[Bug fortran/25149] Compiler dies on -std=f95

2005-11-28 Thread jvdelisle at gcc dot gnu dot org
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2005-11-29 05:53 --- Subject: Bug 25149 Author: jvdelisle Date: Tue Nov 29 05:52:57 2005 New Revision: 107655 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=107655 Log: 2005-11-28 Steven G. Kargl <[EMAI

[Bug fortran/25109] formatted reads with embedded blanks in input fields

2005-11-29 Thread jvdelisle at gcc dot gnu dot org
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2005-11-30 02:09 --- Subject: Bug 25109 Author: jvdelisle Date: Wed Nov 30 02:09:13 2005 New Revision: 107697 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=107697 Log: 2005-11-29 Jerry DeLisle <[EMAI

[Bug fortran/25109] formatted reads with embedded blanks in input fields

2005-11-29 Thread jvdelisle at gcc dot gnu dot org
--- Comment #7 from jvdelisle at gcc dot gnu dot org 2005-11-30 02:53 --- Subject: Bug 25109 Author: jvdelisle Date: Wed Nov 30 02:53:18 2005 New Revision: 107699 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=107699 Log: 2005-11-29 Jerry DeLisle <[EMAI

[Bug fortran/25149] Compiler dies on -std=f95

2005-12-01 Thread jvdelisle at gcc dot gnu dot org
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2005-12-02 00:38 --- Subject: Bug 25149 Author: jvdelisle Date: Fri Dec 2 00:38:36 2005 New Revision: 107851 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=107851 Log: 2005-12-01 Steven G. Kargl <[EMAI

[Bug fortran/25149] Compiler dies on -std=f95

2005-12-01 Thread jvdelisle at gcc dot gnu dot org
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2005-12-02 02:13 --- Fixed in 4.1 and 4.2 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25149

[Bug fortran/25149] Compiler dies on -std=f95

2005-12-01 Thread jvdelisle at gcc dot gnu dot org
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2005-12-02 02:13 --- Closing -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added Status

[Bug fortran/25109] formatted reads with embedded blanks in input fields

2005-12-01 Thread jvdelisle at gcc dot gnu dot org
--- Comment #8 from jvdelisle at gcc dot gnu dot org 2005-12-02 06:10 --- Fixed on 4.1 and 4.2 -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/25251] New: NIST Failure - FM013.f at -O2

2005-12-04 Thread jvdelisle at gcc dot gnu dot org
Failure - FM013.f at -O2 Product: gcc Version: 4.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jvdelisle at gcc dot gnu dot org GCC host t

[Bug libfortran/24459] gfortran namelist problem

2005-12-04 Thread jvdelisle at gcc dot gnu dot org
--- Comment #12 from jvdelisle at gcc dot gnu dot org 2005-12-04 23:11 --- We just had a discussion regarding another similar problem. The maintainers need to come to some concensus on the behavior of some compiler flags such as -std=f95 and -pedantic. Once that is settled then we

[Bug libfortran/25271] gfortran fails to pad lines in format statements to 72 characters.

2005-12-05 Thread jvdelisle at gcc dot gnu dot org
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2005-12-06 02:27 --- I see that g77 output differs from gfortran. I also see gfortran and ifort agree 100%. I am not sure which is right. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25271

[Bug fortran/25264] write to internal unit from the string itself gives wrong result ?

2005-12-05 Thread jvdelisle at gcc dot gnu dot org
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2005-12-06 03:21 --- I can confirm this behavior disagrees with ifort. I will investigate further. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/25264] write to internal unit from the string itself gives wrong result ?

2005-12-06 Thread jvdelisle at gcc dot gnu dot org
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2005-12-07 05:16 --- I have found the offending code. I am working on the fix. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25264

[Bug fortran/24268] gfortran rejects valid format statement

2005-12-07 Thread jvdelisle at gcc dot gnu dot org
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2005-12-08 07:20 --- I am looking into this. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24268

[Bug fortran/25319] namelist error

2005-12-08 Thread jvdelisle at gcc dot gnu dot org
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2005-12-09 02:08 --- I see that ifort gives identical results to gfortran. I believe the correct interpretation is that the read is expecting a list of data and when its not there it ends the read. There are some compilers that

[Bug libfortran/25039] comma short-circuit field width

2005-12-08 Thread jvdelisle at gcc dot gnu dot org
--- Comment #11 from jvdelisle at gcc dot gnu dot org 2005-12-09 02:53 --- Subject: Bug 25039 Author: jvdelisle Date: Fri Dec 9 02:53:41 2005 New Revision: 108271 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=108271 Log: 2005-12-08 Jerry DeLisle <[EMAI

[Bug libfortran/25039] comma short-circuit field width

2005-12-08 Thread jvdelisle at gcc dot gnu dot org
--- Comment #12 from jvdelisle at gcc dot gnu dot org 2005-12-09 02:57 --- Subject: Bug 25039 Author: jvdelisle Date: Fri Dec 9 02:57:13 2005 New Revision: 108272 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=108272 Log: 2005-12-08 Jerry DeLisle <[EMAI

[Bug fortran/25319] namelist error

2005-12-09 Thread jvdelisle at gcc dot gnu dot org
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2005-12-10 00:09 --- Not a bug. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added Status

[Bug libfortran/25307] internal read with end=label aborts

2005-12-10 Thread jvdelisle at gcc dot gnu dot org
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2005-12-10 20:21 --- Where and how end of record or end of file is detected is very sensitive in this code for internal IO. I am currently dredging on 25264 which also has sensitivities. When you work at this long enough you

[Bug fortran/25264] write to internal unit from the string itself gives wrong result ?

2005-12-10 Thread jvdelisle at gcc dot gnu dot org
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2005-12-11 00:32 --- I have this beastie beat. The fix of the initial problem caused no less than 10 regressions (I estimate) and so I had to unmangle that. Talk about head spinning. -- http://gcc.gnu.org/bugzilla/show_bug.cgi

[Bug fortran/25264] write to internal unit from the string itself gives wrong result ?

2005-12-11 Thread jvdelisle at gcc dot gnu dot org
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2005-12-11 08:09 --- Patch submitted for approval. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25264

[Bug libfortran/25349] T edit descriptor broken for output on files

2005-12-11 Thread jvdelisle at gcc dot gnu dot org
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2005-12-11 17:54 --- This is simialr to pr25264. I had to fix a regression in tl-editing, so maybe i need to extend that to the regular files. I was beginning to wonder why internal units seemed so different fromn files. Perhaps

[Bug libfortran/25349] T edit descriptor broken for output on files

2005-12-16 Thread jvdelisle at gcc dot gnu dot org
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2005-12-16 09:04 --- Patch submitted for review and approval. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25349

[Bug fortran/25264] write to internal unit from the string itself gives wrong result ?

2005-12-16 Thread jvdelisle at gcc dot gnu dot org
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2005-12-16 09:05 --- Patch submitted for review and approval. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25264

[Bug libfortran/25349] T edit descriptor broken for output on files

2005-12-16 Thread jvdelisle at gcc dot gnu dot org
--- Comment #7 from jvdelisle at gcc dot gnu dot org 2005-12-16 19:32 --- Subject: Bug 25349 Author: jvdelisle Date: Fri Dec 16 19:32:21 2005 New Revision: 108671 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=108671 Log: 2005-12-16 Jerry DeLisle <[EMAI

[Bug fortran/25264] write to internal unit from the string itself gives wrong result ?

2005-12-16 Thread jvdelisle at gcc dot gnu dot org
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2005-12-16 19:32 --- Subject: Bug 25264 Author: jvdelisle Date: Fri Dec 16 19:32:21 2005 New Revision: 108671 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=108671 Log: 2005-12-16 Jerry DeLisle <[EMAI

[Bug fortran/25264] write to internal unit from the string itself gives wrong result ?

2005-12-16 Thread jvdelisle at gcc dot gnu dot org
--- Comment #7 from jvdelisle at gcc dot gnu dot org 2005-12-16 19:40 --- Subject: Bug 25264 Author: jvdelisle Date: Fri Dec 16 19:40:36 2005 New Revision: 108673 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=108673 Log: 2005-12-16 Jerry DeLisle <[EMAI

[Bug libfortran/25349] T edit descriptor broken for output on files

2005-12-16 Thread jvdelisle at gcc dot gnu dot org
--- Comment #8 from jvdelisle at gcc dot gnu dot org 2005-12-16 19:40 --- Subject: Bug 25349 Author: jvdelisle Date: Fri Dec 16 19:40:36 2005 New Revision: 108673 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=108673 Log: 2005-12-16 Jerry DeLisle <[EMAI

[Bug libfortran/25039] [4.1 only] comma short-circuit field width

2005-12-16 Thread jvdelisle at gcc dot gnu dot org
--- Comment #13 from jvdelisle at gcc dot gnu dot org 2005-12-16 20:37 --- Subject: Bug 25039 Author: jvdelisle Date: Fri Dec 16 20:37:28 2005 New Revision: 108676 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=108676 Log: 2005-12-16 Jerry DeLisle <[EMAI

[Bug libfortran/25039] [4.1 only] comma short-circuit field width

2005-12-16 Thread jvdelisle at gcc dot gnu dot org
--- Comment #14 from jvdelisle at gcc dot gnu dot org 2005-12-16 20:40 --- Subject: Bug 25039 Author: jvdelisle Date: Fri Dec 16 20:40:13 2005 New Revision: 108677 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=108677 Log: 2005-12-16 Jerry DeLisle <[EMAI

[Bug fortran/24268] gfortran rejects valid format statement

2005-12-16 Thread jvdelisle at gcc dot gnu dot org
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2005-12-16 23:44 --- Subject: Bug 24268 Author: jvdelisle Date: Fri Dec 16 23:44:14 2005 New Revision: 108695 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=108695 Log: 2005-12-16 Jerry DeLisle <[EMAI

[Bug fortran/24268] gfortran rejects valid format statement

2005-12-16 Thread jvdelisle at gcc dot gnu dot org
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2005-12-16 23:49 --- Subject: Bug 24268 Author: jvdelisle Date: Fri Dec 16 23:49:33 2005 New Revision: 108696 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=108696 Log: 2005-12-16 Jerry DeLisle <[EMAI

[Bug libfortran/25463] T edit descriptor and ADVANCE="no"

2005-12-17 Thread jvdelisle at gcc dot gnu dot org
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2005-12-17 21:33 --- This simple patch appears to fix this: The stement moved needs to be executed before the return is called. === *** io/transfer.c (revision

[Bug libfortran/25307] internal read with end=label aborts

2005-12-17 Thread jvdelisle at gcc dot gnu dot org
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2005-12-17 21:40 --- I have figured this out. It is similar to the recent tl_editing problems with next_record_w. next_char is not handling the special cases for internal units. I am working up a patch now. -- jvdelisle at gcc

[Bug fortran/25264] write to internal unit from the string itself gives wrong result ?

2005-12-18 Thread jvdelisle at gcc dot gnu dot org
--- Comment #8 from jvdelisle at gcc dot gnu dot org 2005-12-18 08:24 --- Subject: Bug 25264 Author: jvdelisle Date: Sun Dec 18 08:24:04 2005 New Revision: 108744 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=108744 Log: 2005-12-17 Jerry DeLisle <[EMAI

[Bug libfortran/25349] T edit descriptor broken for output on files

2005-12-18 Thread jvdelisle at gcc dot gnu dot org
--- Comment #9 from jvdelisle at gcc dot gnu dot org 2005-12-18 08:24 --- Subject: Bug 25349 Author: jvdelisle Date: Sun Dec 18 08:24:04 2005 New Revision: 108744 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=108744 Log: 2005-12-17 Jerry DeLisle <[EMAI

[Bug fortran/25264] write to internal unit from the string itself gives wrong result ?

2005-12-18 Thread jvdelisle at gcc dot gnu dot org
--- Comment #9 from jvdelisle at gcc dot gnu dot org 2005-12-18 08:32 --- Subject: Bug 25264 Author: jvdelisle Date: Sun Dec 18 08:32:09 2005 New Revision: 108745 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=108745 Log: 2005-12-17 Jerry DeLisle <[EMAI

[Bug libfortran/25349] T edit descriptor broken for output on files

2005-12-18 Thread jvdelisle at gcc dot gnu dot org
--- Comment #10 from jvdelisle at gcc dot gnu dot org 2005-12-18 08:32 --- Subject: Bug 25349 Author: jvdelisle Date: Sun Dec 18 08:32:09 2005 New Revision: 108745 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=108745 Log: 2005-12-17 Jerry DeLisle <[EMAI

[Bug libfortran/25463] T edit descriptor and ADVANCE="no"

2005-12-18 Thread jvdelisle at gcc dot gnu dot org
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2005-12-19 06:52 --- Subject: Bug 25463 Author: jvdelisle Date: Mon Dec 19 06:52:33 2005 New Revision: 108784 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=108784 Log: 2005-12-18 Jerry DeLisle <[EMAI

[Bug libfortran/25463] T edit descriptor and ADVANCE="no"

2005-12-18 Thread jvdelisle at gcc dot gnu dot org
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2005-12-19 07:02 --- Subject: Bug 25463 Author: jvdelisle Date: Mon Dec 19 07:02:05 2005 New Revision: 108785 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=108785 Log: 2005-12-18 Jerry DeLisle <[EMAI

[Bug libfortran/25463] T edit descriptor and ADVANCE="no"

2005-12-18 Thread jvdelisle at gcc dot gnu dot org
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2005-12-19 07:03 --- Commited to 4.2 Will commit to 4.1 in ~24 hours. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25463

[Bug libfortran/25039] [4.1 only] comma short-circuit field width

2005-12-18 Thread jvdelisle at gcc dot gnu dot org
--- Comment #15 from jvdelisle at gcc dot gnu dot org 2005-12-19 07:20 --- Fixed in 4.1 and 4.2 -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/25264] write to internal unit from the string itself gives wrong result ?

2005-12-18 Thread jvdelisle at gcc dot gnu dot org
--- Comment #10 from jvdelisle at gcc dot gnu dot org 2005-12-19 07:22 --- Fixed in 4.1 and 4,2 -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug libfortran/25349] T edit descriptor broken for output on files

2005-12-18 Thread jvdelisle at gcc dot gnu dot org
--- Comment #11 from jvdelisle at gcc dot gnu dot org 2005-12-19 07:23 --- Fixed in 4.1 and 4.2 -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug libfortran/25305] [4.0 regression]: libfortran failed fma3d in SPEC CPU 2K

2005-12-18 Thread jvdelisle at gcc dot gnu dot org
--- Comment #11 from jvdelisle at gcc dot gnu dot org 2005-12-19 07:25 --- Fixed in 4.0, not a bug in 4.1 and 4.2 -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug libfortran/25305] [4.0 regression]: libfortran failed fma3d in SPEC CPU 2K

2005-12-19 Thread jvdelisle at gcc dot gnu dot org
--- Comment #14 from jvdelisle at gcc dot gnu dot org 2005-12-20 00:50 --- My apologies, I was looking at the wrong place. Grigory, thanks for test case. I have regression tested the patch and see no new failures. There are some NIST failures, but these are not affected by the patch

[Bug libfortran/25305] [4.0 regression]: libfortran failed fma3d in SPEC CPU 2K

2005-12-19 Thread jvdelisle at gcc dot gnu dot org
--- Comment #15 from jvdelisle at gcc dot gnu dot org 2005-12-20 05:06 --- Evidently I do not have authorization to commit to the 4.0 branch. (I tried twice) Here is a completed and ready testcase. I strongly suggest people move on to 4.1 if at all possible. If someone else wants to

[Bug libfortran/25305] [4.0 regression]: libfortran failed fma3d in SPEC CPU 2K

2005-12-19 Thread jvdelisle at gcc dot gnu dot org
--- Comment #16 from jvdelisle at gcc dot gnu dot org 2005-12-20 06:06 --- Subject: Bug 25305 Author: jvdelisle Date: Tue Dec 20 06:06:28 2005 New Revision: 108844 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=108844 Log: 2005-12-20 Jerry DeLisle <[EMAI

[Bug libfortran/25305] [4.0 regression]: libfortran failed fma3d in SPEC CPU 2K

2005-12-19 Thread jvdelisle at gcc dot gnu dot org
--- Comment #17 from jvdelisle at gcc dot gnu dot org 2005-12-20 06:12 --- Subject: Bug 25305 Author: jvdelisle Date: Tue Dec 20 06:12:53 2005 New Revision: 108845 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=108845 Log: 2005-12-20 Jerry DeLisle <[EMAI

[Bug libfortran/25305] [4.0 regression]: libfortran failed fma3d in SPEC CPU 2K

2005-12-19 Thread jvdelisle at gcc dot gnu dot org
--- Comment #18 from jvdelisle at gcc dot gnu dot org 2005-12-20 06:19 --- Fixed 4.0 only. Not a bug in 4.1 or 4.2 -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug libfortran/25463] T edit descriptor and ADVANCE="no"

2005-12-20 Thread jvdelisle at gcc dot gnu dot org
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2005-12-21 04:50 --- Subject: Bug 25463 Author: jvdelisle Date: Wed Dec 21 04:50:19 2005 New Revision: 108896 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=108896 Log: 2005-12-20 Jerry DeLisle <[EMAI

[Bug libfortran/25463] T edit descriptor and ADVANCE="no"

2005-12-20 Thread jvdelisle at gcc dot gnu dot org
--- Comment #7 from jvdelisle at gcc dot gnu dot org 2005-12-21 05:09 --- Subject: Bug 25463 Author: jvdelisle Date: Wed Dec 21 05:08:53 2005 New Revision: 108897 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=108897 Log: 2005-12-20 Jerry DeLisle <[EMAI

[Bug libfortran/25510] New: Add ERROR_INTERNAL and ERROR_INTERNAL_UNIT

2005-12-20 Thread jvdelisle at gcc dot gnu dot org
NCONFIRMED Severity: normal Priority: P3 Component: libfortran AssignedTo: jvdelisle at gcc dot gnu dot org ReportedBy: jvdelisle at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25510

[Bug libfortran/25510] Add ERROR_INTERNAL and ERROR_INTERNAL_UNIT

2005-12-20 Thread jvdelisle at gcc dot gnu dot org
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2005-12-21 05:58 --- Possible places to check. If the error is on actual file IO will leave it as is: io/file_pos.c: generate_error (&fpp->common, ERROR_OS, NULL); io/file_pos.c: generate_error (&fpp->common, ERROR

[Bug fortran/24268] gfortran rejects valid format statement

2005-12-20 Thread jvdelisle at gcc dot gnu dot org
--- Comment #7 from jvdelisle at gcc dot gnu dot org 2005-12-21 06:51 --- Subject: Bug 24268 Author: jvdelisle Date: Wed Dec 21 06:51:02 2005 New Revision: 108899 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=108899 Log: 2005-12-20 Jerry DeLisle <[EMAI

[Bug fortran/24268] gfortran rejects valid format statement

2005-12-20 Thread jvdelisle at gcc dot gnu dot org
--- Comment #8 from jvdelisle at gcc dot gnu dot org 2005-12-21 06:52 --- Subject: Bug 24268 Author: jvdelisle Date: Wed Dec 21 06:52:38 2005 New Revision: 108900 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=108900 Log: 2005-12-20 Jerry DeLisle <[EMAI

[Bug fortran/24268] gfortran rejects valid format statement

2005-12-20 Thread jvdelisle at gcc dot gnu dot org
--- Comment #9 from jvdelisle at gcc dot gnu dot org 2005-12-21 06:56 --- This is now fixed for the specific test case. 4.1 and 4.2 are in sync. I plan to go back and review for other possible cases of whitespace. Just want to keep this synchronized. -- http://gcc.gnu.org

[Bug libfortran/25139] [4.1/4.2 regression] "Invalid argument" error on I/O

2005-12-21 Thread jvdelisle at gcc dot gnu dot org
--- Comment #18 from jvdelisle at gcc dot gnu dot org 2005-12-22 01:18 --- This is great! I have regression tested and NIST tested on i686 and all pass. I have not tried some of the problem cases yet, but will do later tonight. I was just getting ready to start working on this one

[Bug libfortran/25139] [4.1/4.2 regression] "Invalid argument" error on I/O

2005-12-21 Thread jvdelisle at gcc dot gnu dot org
--- Comment #19 from jvdelisle at gcc dot gnu dot org 2005-12-22 02:08 --- Ran some test cases. The second example in Comment #3 fails. With or without FX patch given in Comment #6 At line 10 of file back3.f Fortran runtime error: Read past ENDFILE record Dale, are you getting this

[Bug libfortran/25307] internal read with end=label aborts

2005-12-21 Thread jvdelisle at gcc dot gnu dot org
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2005-12-22 02:32 --- Subject: Bug 25307 Author: jvdelisle Date: Thu Dec 22 02:32:29 2005 New Revision: 108938 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=108938 Log: 2005-12-21 Jerry DeLisle <[EMAI

[Bug libfortran/25139] [4.1/4.2 regression] "Invalid argument" error on I/O

2005-12-22 Thread jvdelisle at gcc dot gnu dot org
--- Comment #25 from jvdelisle at gcc dot gnu dot org 2005-12-22 17:59 --- The failure in the second example in comment #3 is that the reading past the record is not being caught by the end specifier in the read statement. It should go to 1011 and continue. This is a different bug

[Bug libfortran/25139] [4.1/4.2 regression] "Invalid argument" error on I/O

2005-12-22 Thread jvdelisle at gcc dot gnu dot org
--- Comment #28 from jvdelisle at gcc dot gnu dot org 2005-12-22 22:49 --- On i686-pc-linux-gnu: $ cat back3.f integer dat(5) dat = (/ 0, 0, 0, 0, 1 /) write(11) dat,dat,dat,dat rewind 11 write(11) dat read(11,end=1008) dat call abort() 1008

[Bug libfortran/25139] [4.1/4.2 regression] "Invalid argument" error on I/O

2005-12-22 Thread jvdelisle at gcc dot gnu dot org
--- Comment #29 from jvdelisle at gcc dot gnu dot org 2005-12-22 23:03 --- Dale, do you have copyright assignment and/or commit priviliges? Also, I have gone to comp.lang.fortran for an interpretation on my comment #28. I see what you are saying and I see what ifort is doing. Ifort

[Bug libfortran/25139] [4.1/4.2 regression] "Invalid argument" error on I/O

2005-12-22 Thread jvdelisle at gcc dot gnu dot org
--- Comment #30 from jvdelisle at gcc dot gnu dot org 2005-12-23 00:21 --- Based on feedback on comp.lang.fortran, the code in #28 is illegal and so the behavior is acceptable and probably appropriate. Based on this I believe we have a working solution to this bug. We just need to

[Bug libfortran/25307] internal read with end=label aborts

2005-12-22 Thread jvdelisle at gcc dot gnu dot org
--- Comment #8 from jvdelisle at gcc dot gnu dot org 2005-12-23 02:02 --- Subject: Bug 25307 Author: jvdelisle Date: Fri Dec 23 02:02:52 2005 New Revision: 109002 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=109002 Log: 2005-12-22 Jerry DeLisle <[EMAI

[Bug libfortran/25307] internal read with end=label aborts

2005-12-22 Thread jvdelisle at gcc dot gnu dot org
--- Comment #9 from jvdelisle at gcc dot gnu dot org 2005-12-23 02:56 --- Subject: Bug 25307 Author: jvdelisle Date: Fri Dec 23 02:56:34 2005 New Revision: 109003 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=109003 Log: 2005-12-22 Jerry DeLisle <[EMAI

[Bug libfortran/25307] internal read with end=label aborts

2005-12-22 Thread jvdelisle at gcc dot gnu dot org
--- Comment #10 from jvdelisle at gcc dot gnu dot org 2005-12-23 02:59 --- Subject: Bug 25307 Author: jvdelisle Date: Fri Dec 23 02:59:37 2005 New Revision: 109005 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=109005 Log: 2005-12-22 Jerry DeLisle <[EMAI

[Bug libfortran/25307] internal read with end=label aborts

2005-12-22 Thread jvdelisle at gcc dot gnu dot org
--- Comment #11 from jvdelisle at gcc dot gnu dot org 2005-12-23 05:54 --- Fixed on 4.1 and 4.2 -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug libfortran/25463] T edit descriptor and ADVANCE="no"

2005-12-22 Thread jvdelisle at gcc dot gnu dot org
--- Comment #8 from jvdelisle at gcc dot gnu dot org 2005-12-23 05:57 --- Fixed on 4.1 and 4.2 -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug libfortran/25139] [4.1/4.2 regression] "Invalid argument" error on I/O

2005-12-23 Thread jvdelisle at gcc dot gnu dot org
--- Comment #32 from jvdelisle at gcc dot gnu dot org 2005-12-23 20:21 --- Yes, I will work this up with a proper test case and submit for approval. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25139

[Bug libfortran/25419] gfortran read does not take comma for default on one entry

2005-12-25 Thread jvdelisle at gcc dot gnu dot org
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2005-12-26 06:00 --- I have a fix for this already. Patch for submottal soon. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug libfortran/25550] file data corrupted after reading end of file

2005-12-26 Thread jvdelisle at gcc dot gnu dot org
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2005-12-27 04:00 --- I have a fix for this. Will submit shortly. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug libfortran/25419] gfortran read does not take comma for default on one entry

2005-12-27 Thread jvdelisle at gcc dot gnu dot org
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2005-12-28 06:59 --- Subject: Bug 25419 Author: jvdelisle Date: Wed Dec 28 06:59:35 2005 New Revision: 109099 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=109099 Log: 2005-12-28 Jerry DeLisle <[EMAI

[Bug libfortran/25419] gfortran read does not take comma for default on one entry

2005-12-27 Thread jvdelisle at gcc dot gnu dot org
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2005-12-28 07:00 --- Subject: Bug 25419 Author: jvdelisle Date: Wed Dec 28 07:00:47 2005 New Revision: 109100 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=109100 Log: 2005-12-28 Jerry DeLisle <[EMAI

[Bug libfortran/25550] file data corrupted after reading end of file

2005-12-27 Thread jvdelisle at gcc dot gnu dot org
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2005-12-28 07:20 --- Subject: Bug 25550 Author: jvdelisle Date: Wed Dec 28 07:20:19 2005 New Revision: 109101 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=109101 Log: 2005-12-28 Jerry DeLisle <[EMAI

[Bug libfortran/25550] file data corrupted after reading end of file

2005-12-27 Thread jvdelisle at gcc dot gnu dot org
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2005-12-28 07:21 --- Subject: Bug 25550 Author: jvdelisle Date: Wed Dec 28 07:21:20 2005 New Revision: 109102 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=109102 Log: 2005-12-28 Jerry DeLisle <[EMAI

[Bug fortran/25587] New: Garbage in output of -fdump-tree-original

2005-12-27 Thread jvdelisle at gcc dot gnu dot org
: 4.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran 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=25587

[Bug libfortran/25139] [4.1/4.2 regression] "Invalid argument" error on I/O

2005-12-28 Thread jvdelisle at gcc dot gnu dot org
--- Comment #33 from jvdelisle at gcc dot gnu dot org 2005-12-28 20:58 --- Subject: Bug 25139 Author: jvdelisle Date: Wed Dec 28 20:58:08 2005 New Revision: 109122 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=109122 Log: 2005-12-28 Jerry DeLisle <[EMAI

[Bug libfortran/25510] Add ERROR_INTERNAL and ERROR_INTERNAL_UNIT

2005-12-28 Thread jvdelisle at gcc dot gnu dot org
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2005-12-28 20:58 --- Subject: Bug 25510 Author: jvdelisle Date: Wed Dec 28 20:58:08 2005 New Revision: 109122 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=109122 Log: 2005-12-28 Jerry DeLisle <[EMAI

[Bug libfortran/25139] [4.1/4.2 regression] "Invalid argument" error on I/O

2005-12-28 Thread jvdelisle at gcc dot gnu dot org
--- Comment #34 from jvdelisle at gcc dot gnu dot org 2005-12-28 21:12 --- Subject: Bug 25139 Author: jvdelisle Date: Wed Dec 28 21:12:52 2005 New Revision: 109123 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=109123 Log: 2005-12-28 Jerry DeLisle <[EMAI

<    1   2   3   4   5   6   7   8   9   10   >