This is the mail archive of the
mailing list for the GCC project.
Migration to target hooks
- From: Kazu Hirata <kazu at cs dot umass dot edu>
- To: gcc at gcc dot gnu dot org
- Date: Sun, 18 Jan 2004 10:48:01 -0500 (EST)
- Subject: Migration to target hooks
Speaking of hookizing...
A few days ago, I hookized most of target macros that are easy to
hookize. (I am only alleviating the half migration issue, not
creating new nooks, though.) I am thinking about submitting a patch
for one port at a time (instead of one macro at a time across all the
ports) for easier approvals. Any objections?
FYI, I took care of most of
By the way, some sub-targets override the corresponding target macros.
Is there any good way of handling this? arm's RETURN_IN_MEMORY and
m68k's STRUCT_VALUE_REGNUM come to mind. Define a macro that
indicates the sub-target in a sub-target header file (if not already
defined), and then reference it in tm.c?