[Bug fortran/45030] New: -fwhole-file: Bogus error message with ENTRY and different result types

[Bug fortran/45030] New: -fwhole-file: Bogus error message with ENTRY and different result types

[burnus at gcc dot gnu dot org]

This is a bug which needs to be fixed before -fwhole-file can be enabled by
default. Otherwise, the test results look fine. (Note: I tested with
-fwhole-file enabled by default and including the patch for PR 44945.)


Extended test case: gfortran.fortran-torture/execute/entry_4.f90


real,    external :: g
                      1
Error: Return type mismatch of function 'g' at (1) (REAL(4)/INTEGER(4))


Test case:

function f()
  integer :: f
  real :: g
entry g()
end function

integer, external :: f
real,    external :: g
integer :: ff
real :: gg
ff = f()
gg = g()
end


-- 
           Summary: -fwhole-file: Bogus error message with ENTRY and
                    different result types
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Keywords: rejects-valid
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: burnus at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45030

[Bug fortran/45030] -fwhole-file: Bogus error message with ENTRY and different result types

[burnus at gcc dot gnu dot org]

------- Comment #1 from burnus at gcc dot gnu dot org  2010-07-22 13:42 -------
Another test case is: libgomp.fortran/retval1.f90
(Found via "cd $BUILD/*/libgomp; make check")


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45030

[Bug fortran/45030] -fwhole-file: Bogus error message with ENTRY and different result types

[burnus at gcc dot gnu dot org]

------- Comment #2 from burnus at gcc dot gnu dot org  2010-07-23 11:24 -------
Created an attachment (id=21293)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=21293&action=view)
Draft patch

Draft patch. I was wondering whether one needs to take care of

(a) use names in case of use association - or can one not reach that function
in this case?

(b) C binding names, i.e.

subroutine foo() bind(C, name=bar)
...
entry foo2() bind(C, name=bar2)
...
end

interface
  subroutine Hello() bind(C,name=bar2)
  end
end interface

call Hello() ! << this should use the same backend decl as "ENTRY foo2".

(c) Whether this just fixes the error checking or whether the backend_decl is
also correct.

What do you think, Paul?


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45030

[Bug fortran/45030] -fwhole-file: Bogus error message with ENTRY and different result types

[burnus at gcc dot gnu dot org]

------- Comment #3 from burnus at gcc dot gnu dot org  2010-07-23 20:07 -------
Subject: Bug 45030

Author: burnus
Date: Fri Jul 23 20:07:30 2010
New Revision: 162486

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=162486
Log:
2010-07-23  Tobias Burnus  <burnus@net-b.de>

        PR fortran/45030
        * resolve.c (resolve_global_procedure): Properly handle ENTRY.


Modified:
    trunk/gcc/fortran/ChangeLog
    trunk/gcc/fortran/resolve.c


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45030

[Bug fortran/45030] -fwhole-file: Bogus error message with ENTRY and different result types

[burnus at gcc dot gnu dot org]

------- Comment #4 from burnus at gcc dot gnu dot org  2010-07-23 20:08 -------
The ENTRY diagnostics issue of comment 0 is now fixed. I leave the PR open
until one has checked the issues raised in comment 1.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45030

[Bug fortran/45030] -fwhole-file: Bogus error message with ENTRY and different result types

[burnus at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45030

Tobias Burnus <burnus at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |RESOLVED
         Resolution|                            |FIXED

--- Comment #6 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-12-16 07:12:15 UTC ---
Let's mark it as fixed. There are probably still some issues, but it seems as
if comment 1 is (mostly) fine.

[Bug fortran/45030] -fwhole-file: Bogus error message with ENTRY and different result types

[dominiq at lps dot ens.fr]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45030

Dominique d'Humieres <dominiq at lps dot ens.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING
   Last reconfirmed|                            |2011-12-15
     Ever Confirmed|0                           |1

--- Comment #5 from Dominique d'Humieres <dominiq at lps dot ens.fr> 2011-12-15 21:37:01 UTC ---
AFAICT the issues raised in comment #1 is fixed at least on 4.6.2 and trunk.
Tobias could you please confirm it?