> So, I can bootstrap and regtested this on i686-linux, x86_64-linux, and
> x86_64-darwin. Other platforms, I don't have access to or have trouble
> bootstrapping at all (mingw, I'm looking at you!). My question, thus is:
> what testing is required for this?
You must at least build a cross-compile
Another question cropping up for me is: what are the testing requirements for a
patch of that nature? The final list of files touched in gcc/config/ is:
M alpha/linux.h
M alpha/alpha.h
M alpha/osf5.h
M alpha/netbsd.h
M frv/frv.h
M spu/spu-protos.h
M spu/s
> 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
> pur
On Mon, 4 Oct 2010, FX wrote:
> The attached patch is my first attempt to deal with
> TARGET_CPU_CPP_BUILTINS macros by splitting them into
> language-independent and C-family parts. This is now more like a
> demonstration of how I intend to proceed, by creating a new macro
> TARGET_CPU_CPP_BU
