aboutsummaryrefslogtreecommitdiff
path: root/manual/examples/search.c
diff options
context:
space:
mode:
authorJoseph Myers <joseph@codesourcery.com>2017-03-16 17:51:23 +0000
committerJoseph Myers <joseph@codesourcery.com>2017-03-16 17:51:23 +0000
commit0fbca26c39e4735e7285092c98c75500550d84f4 (patch)
treefffe5c50a74acd56984220ab153ea783cd54a35c /manual/examples/search.c
parent598fe6d9f4c860fe084abb769510a4636fe8f293 (diff)
downloadglibc-0fbca26c39e4735e7285092c98c75500550d84f4.tar
glibc-0fbca26c39e4735e7285092c98c75500550d84f4.tar.gz
glibc-0fbca26c39e4735e7285092c98c75500550d84f4.tar.bz2
glibc-0fbca26c39e4735e7285092c98c75500550d84f4.zip
conformtest: Make more tests into compilation tests.
The conformtest header tests test some things through compilation tests and others through execution tests. This patch makes more of the tests into compilation tests, using _Static_assert (note: for float.h tests on floating-point values this is depending on a GNU extension, that those assertions are allowed in the absence of -pedantic although they aren't strictly integer constant expressions). The remaining execution tests are for values of things listed as "symbol" (in fact no such things have a value expectation listed) and for values of macros defined as string constants (three such values listed in total). This is intended as preparation for enabling the vast bulk of the tests to run for cross compilation. (Even the few remaining execution tests ought in principle to run for cross compilation when a test wrapper is defined, but that's more complicated. The existing execution tests for native builds in fact are linked and run with an existing installed libc that's required to exist to link against, rather than with the newly built libc; only the new headers are used.) Tested for x86_64. * conform/conformtest.pl: Use compilation instead of execution tests for testing values of constants and usability in #if.
Diffstat (limited to 'manual/examples/search.c')
0 files changed, 0 insertions, 0 deletions