This is the mail archive of the
mailing list for the GCC project.
Re: Proposed targets to deprecate for 3.4
- From: "Zack Weinberg" <zack at codesourcery dot com>
- To: Hans-Peter Nilsson <hp at bitrange dot com>
- Cc: Nathanael Nerode <neroden at twcny dot rr dot com>, <gcc at gcc dot gnu dot org>
- Date: Wed, 01 Oct 2003 11:00:34 -0700
- Subject: Re: Proposed targets to deprecate for 3.4
- References: <Pine.BSF.firstname.lastname@example.org>
Hans-Peter Nilsson <email@example.com> writes:
> On Wed, 1 Oct 2003, Zack Weinberg wrote:
>> Hans-Peter Nilsson <firstname.lastname@example.org> writes:
>> >> There has got to be a better way to do that.
>> > Perhaps a (new) TARGET_ASM_FUNCTION_BEGIN_PROLOGUE? If you're
>> > opposed to TARGET_ASM_FUNCTION_END_PROLOGUE, look at alpha.
>> No, I'm not opposed to ..._END_PROLOGUE; it has a well-defined task
>> that doesn't overlap with another mechanism. Could you use
>> ASM_FUNCTION_START for what you need, maybe?
> What's that? A new macro? :-) (Sorry, I see no useful macro
> matching *FUNCTION*.) Still, it'd just be trading one for
I believe I was thinking of ASM_DECLARE_FUNCTION_NAME. Anyway, the
suggestion to use prologue_epilogue_contains seems like the Right
Thing to me.