This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] testsuite: Add new effective target keywords
- From: Björn Haase <bjoern dot m dot haase at web dot de>
- To: Paul Brook <paul at codesourcery dot com>
- Cc: gcc-patches at gcc dot gnu dot org,Janis Johnson <janis187 at us dot ibm dot com>
- Date: Mon, 18 Apr 2005 09:02:11 +0200
- Subject: Re: [PATCH] testsuite: Add new effective target keywords
- References: <200504072320.46784.bjoern.m.haase@web.de> <200504180028.37403.bjoern.m.haase@web.de> <200504180218.25992.paul@codesourcery.com>
Am Montag, 18. April 2005 03:18 schrieb Paul Brook:
> On Sunday 17 April 2005 23:28, Björn Haase wrote:
> > Hi,
> >
> > when preparing to prepare the testsuite to be better adapted also for
> > small targets, I have made use of the approach that you had suggested.
> > You will find attached a patch that defines three new effective-target
> > keywords:
> >
> > nested_functions
> > trampolines
>
> Why do you need to check for these two separately? Isn't the "trampolines"
> test sufficient to cover all the problematic uses of nested functions?
>
... I agree that it's possibly rather a technical issue: I meant
"nested_functions" to be more restrictive than "trampolines": In the case of
Harvard-Architectures with read-only program memory space (like AVR), it will
*allways* be impossible to implement trampolines. Limited nested function
support, however, possibly could be implemented without trampolines.? E.g, it
seems that avr-ada already realizes limited nested function support that is
functional as long as the address of the nested function is not passed to the
world outside the wrapper-function. I do not expect that this subtle
distinction will be of importance for AVR in the near future but I never the
less thought two keywords to be the more appropriate way.
Yours,
Björn