[Bug fortran/29689] gfortran should use g77-compatible format for error message
--- Comment #8 from brooks at gcc dot gnu dot org 2006-11-09 23:17 --- Fixed on 4.2: svn 118628. -- brooks at gcc dot gnu dot org changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29689
[Bug fortran/29689] gfortran should use g77-compatible format for error message
--- Comment #7 from brooks dot moses at codesourcery dot com 2006-11-07 04:28 --- Patch posted for 4.2 but not yet approved: http://gcc.gnu.org/ml/fortran/2006-11/msg00150.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29689
[Bug fortran/29689] gfortran should use g77-compatible format for error message
-- brooks at gcc dot gnu dot org changed: What|Removed |Added AssignedTo|unassigned at gcc dot gnu |brooks at gcc dot gnu dot |dot org |org Status|NEW |ASSIGNED Last reconfirmed|2006-11-02 14:01:54 |2006-11-07 04:33:24 date|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29689
[Bug fortran/29689] gfortran should use g77-compatible format for error message
--- Comment #6 from tkoenig at gcc dot gnu dot org 2006-11-05 21:31 --- I don't know why I assigned this to myself. Brooks has already fixed this. Unassigning myself. -- tkoenig at gcc dot gnu dot org changed: What|Removed |Added AssignedTo|tkoenig at gcc dot gnu dot |unassigned at gcc dot gnu |org |dot org Status|ASSIGNED|NEW http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29689
[Bug fortran/29689] gfortran should use g77-compatible format for error message
--- Comment #4 from fxcoudert at gcc dot gnu dot org 2006-11-03 14:14 --- Commited to mainline as revision 118450. Maybe we want to include this into 4.2 before 4.2.0 is released? I think that would be the best thing to do; opinions? -- fxcoudert at gcc dot gnu dot org changed: What|Removed |Added AssignedTo|unassigned at gcc dot gnu |tkoenig at gcc dot gnu dot |dot org |org Status|NEW |ASSIGNED Keywords||patch Known to fail||4.1.2 4.2.0 Known to work||4.3.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29689
[Bug fortran/29689] gfortran should use g77-compatible format for error message
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2006-11-03 16:12 --- I agree and already tested for Brooks on 4.2 last night. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29689
[Bug fortran/29689] gfortran should use g77-compatible format for error message
-- fxcoudert at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last reconfirmed|-00-00 00:00:00 |2006-11-02 14:01:54 date|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29689
[Bug fortran/29689] gfortran should use g77-compatible format for error message
--- Comment #1 from fxcoudert at gcc dot gnu dot org 2006-11-02 14:34 --- Some incomplete patch proposals here: http://gcc.gnu.org/ml/fortran/2006-10/msg00825.html and there: http://gcc.gnu.org/ml/fortran/2006-11/msg00017.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29689
[Bug fortran/29689] gfortran should use g77-compatible format for error message
--- Comment #2 from brooks dot moses at codesourcery dot com 2006-11-03 02:52 --- Created an attachment (id=12541) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12541action=view) Proposed patch including testsuite changes I attempted to send this to the list, but I'm not sure if it went through. Thus, posting it here; the following text had been included in the email: Steve Kargl wrote: I have stated more than once THE TRIVIAL FIX DOES NOT WORK. It causes REGRESSIONS in the gfortran testsuite. If someone wants to fix whatever is causing the regressions, I'll be more than happy to commit the patch. The attached only-slightly-less-trivial patch should fix the regressions, although I have not yet tested it to confirm that. Since my build machine is currently occupied with running CFD calculations for my dissertation, would you mind regtesting it? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29689
[Bug fortran/29689] gfortran should use g77-compatible format for error message
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2006-11-03 04:07 --- I will give it a spin -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29689