[PATCH] support: Introduce new subdirectory for test infrastructure

[Carlos O'Donell]

On 11/29/2016 01:41 AM, Florian Weimer wrote:
> On 11/29/2016 12:11 AM, Joseph Myers wrote:
>> In the new style, what is the recommended way of doing a
>> compile-only test (tests that presently do "#define TEST_FUNCTION
>> 0", like elf/tst-linkall-static.c)?  Define a dummy test function
>> that just returns 0?
> 
> Yes, that would be my preference for the time being.  I hope that we
> will get real compile-time tests eventually.  we really need them to
> check the fortify functionality and its warnings and errors.

That's certainly a use case that has failure modes we need to test.

I spent quite a while trying to get compile-time tests to work and there is a
lot of surgery required to make it work as expected and have the overrides
work correctly.

Even then the final solution I had was overly simplistic and didn't allow
layering of tests because the source to test mapping was quite simple.

FYI: https://sourceware.org/ml/libc-alpha/2016-06/msg00162.html

-- 
Cheers,
Carlos.