Re: PPC -mlongcall, take two

[Zack Weinberg <zack at codesourcery dot com>]

On Sun, May 12, 2002 at 06:51:30AM -0700, Stan Shebs wrote:
> 
> > Should we check in rs6000.h for
> > if !defined REGISTER_TARGET_PRAGMAS
> > define REGISTER_TARGET_PRAGMAS
> > fi
> > And add the longcall pragma to darwin.h?
> 
> config/darwin* is supposed to be processor-neutral, and indeed
> I have a set of patches for x86 Darwin almost ready to submit,
> so it can't go in there.  Perhaps the right thing is to introduce
> a second macro, and either invoke it directly from c-pragma.c,
> or from the Darwin macro (it's all just registering of pragmas,
> not finicky about ordering or anything like that).  The second
> choice is lower impact, better since this whole situation is
> kind of an oddball.

However, the second choice would require you to modify the cpu.h file
of any target that has a Darwin port.  I think it makes more sense to
have split CPU and OS pragma registration hooks in the same way that
we now have split CPU and OS builtin-macro registration hooks.

Come to think of it, is there any reason not to fold pragma
registration into the builtin-macro registration hooks?

Neil, thoughts?

zw