This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Patch for having internal macros as functions, take 2
- To: Hans-Peter Nilsson <hp at bitrange dot com>
- Subject: Re: Patch for having internal macros as functions, take 2
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Tue, 04 Jan 2000 00:43:29 -0700
- cc: Horst von Brand <vonbrand at sleipnir dot valparaiso dot cl>, gcc-patches at gcc dot gnu dot org
- Reply-To: law at cygnus dot com
In message <Pine.BSF.4.10.10001021644200.7969-100000@dair.pair.com>you write:
> You also cannot "functionalize" macros that use alloca, or where a
> parameter is code or a label, like GO_IF_LEGITIMIZE_ADDRESS. So you can't
> add a PROVIDE_MACRO_FUNCTION marker for them. However, the vast majority
> of macros in gcc are function-like.
I believe Meissner pointed out that you can functionalize those macros, in
fact several ports already do.
In fact, I would recommend to folks writing ports that they functionalize
stuff like GO_IF_LEGITIMATE_ADDRESS, FUNCTION_ARG, etc etc if they
grow to more than a few lines of code.
I've always considered it rather lame to have to mentally debug page
long macros. Even given dwarf2 macro debugging capabilities, at some
point page-long macros just become rather silly.
jeff