On Wed, 2 Aug 2017, Martin Sebor wrote: > If there is no way, would enhancing target-supports.exp to > include a header that defines the macro? (I assume that would > be gcc/target.h for FUNCTION_BOUNDARY).
target.h is for target hooks, not target macros, and we want to move away from target macros, so adding dependencies on the existence of a macro with this value doesn't seem like a good idea (anyway, FUNCTION_BOUNDARY can depend on command-line options passed to the compiler, so getting it from a compiler header can't possibly work). We have -fbuilding-libgcc to pass configuration to target library builds that shouldn't otherwise be needed in normal user code built by GCC (via defining extra predefined macros if that option is passed). I suppose you could have something like that to provide such information to the testsuite. -- Joseph S. Myers jos...@codesourcery.com