[Bug fortran/39290] Subroutine/function ambiguity in generics

2015-12-05 Thread jvdelisle at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=39290 Jerry DeLisle changed: What|Removed |Added CC||Joost.VandeVondele at mat dot ethz

[Bug fortran/39290] Subroutine/function ambiguity in generics

2013-07-15 Thread burnus at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39290 --- Comment #11 from Tobias Burnus --- See also PR 20896 - and the test case at http://gcc.gnu.org/ml/fortran/2013-07/msg00017.html

[Bug fortran/39290] Subroutine/function ambiguity in generics

2013-04-29 Thread janus at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39290 --- Comment #10 from janus at gcc dot gnu.org 2013-04-29 14:53:03 UTC --- (In reply to comment #9) > BTW: When updating this, one can also implement the new Fortran 2008 feature: > "ALLOCATABLE and POINTER attributes are used in generic reso

[Bug fortran/39290] Subroutine/function ambiguity in generics

2013-04-29 Thread burnus at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39290 --- Comment #9 from Tobias Burnus 2013-04-29 12:40:50 UTC --- (In reply to comment #8) > There are a quite a few problems it seems: > 1. we rely on s1->attr.function _and_ s2->attr.function being set, which is > obviously not the case with impl

[Bug fortran/39290] Subroutine/function ambiguity in generics

2013-04-29 Thread mikael at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39290 --- Comment #8 from Mikael Morin 2013-04-29 10:59:51 UTC --- The following excerpt from gfc_compare_interfaces(interface.c) seems to be the cause of 'qc' being called: if (s1->attr.function && s2->attr.function) { /* If

[Bug fortran/39290] Subroutine/function ambiguity in generics

2013-04-29 Thread burnus at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39290 Tobias Burnus changed: What|Removed |Added CC||burnus at gcc dot gnu.org --- C

[Bug fortran/39290] Subroutine/function ambiguity in generics

2013-04-28 Thread janus at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39290 janus at gcc dot gnu.org changed: What|Removed |Added CC||janus at gcc dot gnu.org

[Bug fortran/39290] Subroutine/function ambiguity in generics

2012-08-18 Thread mikael at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39290 --- Comment #5 from Mikael Morin 2012-08-18 22:00:20 UTC --- Author: mikael Date: Sat Aug 18 22:00:10 2012 New Revision: 190504 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=190504 Log: Add the working testcase from PR fortran/39290. te

[Bug fortran/39290] Subroutine/function ambiguity in generics

2012-08-18 Thread mikael at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39290 --- Comment #4 from Mikael Morin 2012-08-18 21:56:02 UTC --- (In reply to comment #3) > Thus, I concur that it seems to be fixed. However, one could consider to > include the two test cases of the IR in the testsuite - besides the invalid > one

[Bug fortran/39290] Subroutine/function ambiguity in generics

2012-08-12 Thread burnus at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39290 Tobias Burnus changed: What|Removed |Added CC||burnus at gcc dot gnu.org --- Comment #3

[Bug fortran/39290] Subroutine/function ambiguity in generics

2012-08-12 Thread mikael at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39290 Mikael Morin changed: What|Removed |Added CC||mikael at gcc dot gnu.org --- Comment #2 f

[Bug fortran/39290] Subroutine/function ambiguity in generics

2009-02-26 Thread pault at gcc dot gnu dot org
--- Comment #1 from pault at gcc dot gnu dot org 2009-02-26 12:27 --- This is the same as PR20896, isn't it? Maybe I should pick that up once more Paul -- pault at gcc dot gnu dot org changed: What|Removed |Added -