global.c goofyness

[Joern Rennecke]

In article < orogd55kgs.fsf@garnize.lsd.ic.unicamp.br > you wrote:
...
: Would this patch fix it?
...
: 	* global.c (wrap_IOR_HARD_REG_SET): New function.
: 	(prune_preferences, find_reg): Use it.

If we really want a kludge just to protect IOR_HARD_REG_SET from being
expanded into several macro arguments, we could just change the 5 definitions
of the macro that use commas to use separate declarations of scan_tp_ and
scan_fp_ instead.

But this entire approach (i.e. just changing the argument passed to
EXECUTE_IF_CONFLICT) is fragile, since later someone might want to
put some other piece of code into an EXECUTE_IF_CONFLICT macro call,
and we'll see the same problem again.