[RFC] Moving TM builtin creation to the machine independent parts of the compiler

[Michael Meissner <meissner at linux dot vnet dot ibm dot com>]

As we were discussing Thursday on IRC, the powerpc port doesn't set up the
attributes correctly for the builtin functions.  Richard Henderson suggested
making the backend builtin creation to use the same infrastructure as the
normal builtins, so that we can use the types and attributes for the builtins.

I was wondering if the following work in progress is what was suggested.
Basically, it allows the target machine to define a set of *.def files that are
handled inside of builtins.def and builtin-types.def and builtin-attrs.def.
Right now, I don't anticipate needing to do the attributes, but I figure to put
in the support in case some other backend needs it.

This patch creates tm-builtins-headers.def, tm-builtins-types.def, and
tm-builtins-attrs.def in the build directory to include the various tm builtin
files.  At the moment, I'm including one builtin, before tackling the 900 or so
powerpc builtins.

I suspect I should use the s-* and moveifchange mecanism in the Makefile.

-- 
Michael Meissner, IBM
4 Technology Place Drive, MS 2203A, Westford, MA, 01886, USA
meissner@linux.vnet.ibm.com

Attachment: gcc-power7.patch79
Description: Text document