This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: [RFC] Dealing with TARGET_CPU_CPP_BUILTINS
> I don't think you need define_target_specific_builtins as part of the
> public interface to cppbuiltin.c; it will always be called along with
> define_language_independent_builtin_macros so may as well be called
> internally by that function (which could gain an iso_c parameter for that
> purpose).
Sure.
> I suppose calling cpp_define directly in target .c files (and generally
> not having a separate set of preprocessor-using-front-end-hooks) is safe
> in that all front ends are linked with cpplib, though I think the reason
> they are so linked at present is just for the line-map code.
In the longer term, it sure makes sense to move all this to a more generic hooks-based mechanism.
FX