[Bug fortran/36325] specific or generic INTERFACE implies the EXTERNAL attribute

2008-05-28 Thread janus at gcc dot gnu dot org
--- Comment #13 from janus at gcc dot gnu dot org 2008-05-28 21:37 --- Fixed with r136130. Closing. -- janus at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/36325] specific or generic INTERFACE implies the EXTERNAL attribute

2008-05-28 Thread janus at gcc dot gnu dot org
--- Comment #12 from janus at gcc dot gnu dot org 2008-05-28 21:28 --- Subject: Bug 36325 Author: janus Date: Wed May 28 21:27:56 2008 New Revision: 136130 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=136130 Log: 2008-05-28 Janus Weil <[EMAIL PROTECTED]> PR fortran/

[Bug fortran/36325] specific or generic INTERFACE implies the EXTERNAL attribute

2008-05-25 Thread janus at gcc dot gnu dot org
--- Comment #8 from janus at gcc dot gnu dot org 2008-05-25 22:33 --- The failure of proc_decl_9.f90 was actually due to a bug that slipped in with my procedure declaration update patch from May 1st, which I have fixed now. So we're left with gomp/reduction3.f90, which contains this pie

[Bug fortran/36325] specific or generic INTERFACE implies the EXTERNAL attribute

2008-05-25 Thread burnus at gcc dot gnu dot org
--- Comment #7 from burnus at gcc dot gnu dot org 2008-05-25 19:58 --- > Patch is attached. You need also to reject the following, which violates R504. interface real function bar() end function bar end interface dimension :: bar(4) end -- http://gcc.gnu.org/bugzilla/show_bug.

[Bug fortran/36325] specific or generic INTERFACE implies the EXTERNAL attribute

2008-05-25 Thread janus at gcc dot gnu dot org
--- Comment #6 from janus at gcc dot gnu dot org 2008-05-25 19:08 --- Created an attachment (id=15684) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15684&action=view) patch Ok, I extended the patch, and got the regression count down from a few million to exactly two: FAIL: gfort

[Bug fortran/36325] specific or generic INTERFACE implies the EXTERNAL attribute

2008-05-25 Thread burnus at gcc dot gnu dot org
--- Comment #5 from burnus at gcc dot gnu dot org 2008-05-25 17:11 --- > Which leads me to think we should probably implement this (for the case that > the interface is explicit). Or is there any good reason that this is not done? Well, regarding the reason: Before interfaces had no EXT

[Bug fortran/36325] specific or generic INTERFACE implies the EXTERNAL attribute

2008-05-25 Thread janus at gcc dot gnu dot org
--- Comment #4 from janus at gcc dot gnu dot org 2008-05-25 16:37 --- (In reply to comment #2) > Others testcases (like argument_checking_3.f90) fail because they define lots > of specific interfaces, but no external implementation for those. Obviously I got this wrong. The actual reaso

[Bug fortran/36325] specific or generic INTERFACE implies the EXTERNAL attribute

2008-05-25 Thread burnus at gcc dot gnu dot org
--- Comment #3 from burnus at gcc dot gnu dot org 2008-05-25 15:36 --- > Ok, this produces an impressive list of regressions. > Many of those (e.g. actual_procedure_1.f90) seem to be related to > conf (external, dimension); /* See Fortran 95's R504. */ > I'm not sure if the constrai

[Bug fortran/36325] specific or generic INTERFACE implies the EXTERNAL attribute

2008-05-25 Thread jaydub66 at gmail dot com
--- Comment #2 from jaydub66 at gmail dot com 2008-05-25 14:45 --- Ok, this produces an impressive list of regressions. Many of those (e.g. actual_procedure_1.f90) seem to be related to conf (external, dimension); /* See Fortran 95's R504. */ I'm not sure if the constraint from R

[Bug fortran/36325] specific or generic INTERFACE implies the EXTERNAL attribute

2008-05-25 Thread jaydub66 at gmail dot com
--- Comment #1 from jaydub66 at gmail dot com 2008-05-25 14:02 --- Here is a first patch: Index: gcc/fortran/symbol.c === --- gcc/fortran/symbol.c(revision 135859) +++ gcc/fortran/symbol.c(working copy) @@ -