This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [gfortran] Make all arguments to ENTRY master optional

From: Tobias Schlüter <tobias dot schlueter at physik dot uni-muenchen dot de>
To: Paul Brook <paul at codesourcery dot com>
Cc: fortran at gcc dot gnu dot org, Steven Bosscher <stevenb at suse dot de>,patch <gcc-patches at gcc dot gnu dot org>
Date: Tue, 24 Aug 2004 18:35:24 +0200
Subject: Re: [gfortran] Make all arguments to ENTRY master optional
References: <412B5A5F.6050205@physik.uni-muenchen.de> <200408241718.02723.stevenb@suse.de> <412B5F62.3050500@physik.uni-muenchen.de> <200408241721.08952.paul@codesourcery.com>

Paul Brook wrote:
> No. The special handling is there for a reason.
> I've added the following to the testsuite.
> 
> Because the master arguments are shared with the individual entry points, I 
> think you'd also end up (incorrectly) allowing:
> call foo()

I missed that. This problem exists because we call resolve_entries in the
_beginning_ of gfc_resolve. I admit that introducing an order-dependency is
not a good thing.

Thanks,
- Tobi

Follow-Ups:
- Re: [gfortran] Make all arguments to ENTRY master optional
  - From: Paul Brook

References:
- [gfortran] Make all arguments to ENTRY master optional
  - From: Tobias Schlüter
- Re: [gfortran] Make all arguments to ENTRY master optional
  - From: Steven Bosscher
- Re: [gfortran] Make all arguments to ENTRY master optional
  - From: Tobias Schlüter
- Re: [gfortran] Make all arguments to ENTRY master optional
  - From: Paul Brook

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]