This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Converting tm.h macros to functions


One thing that has been mentioned from time to time is that a lot of tm.h
macros (such as ASM_OUTPUT_*) should really be proper functions with
documented prototypes.  Some questions about the details of how this
should be done:

* Where should the default versions of these functions go?  In random
source files, or in a new defaults.c?

* How should a target indicate that it has its own version of one of these
functions?  Should a macro be used (e.g., defining HAVE_asm_output_ascii
to indicate that the target has its own asm_output_ascii function and the
default one should not be compiled in) or should function pointers be
used, initialised to the default function and changed (where?) by the back
end to point to the back-end-specific version?

-- 
Joseph S. Myers
jsm28@cam.ac.uk


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]