https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108675
--- Comment #2 from nightstrike <nightstrike at gmail dot com> --- (In reply to Richard Biener from comment #1) > These tests are known to be a bit awkwardly implemented to check for > optimizations done ... How would you do it if you were writing the test today? > There might be a better way to provide definitions of fprintf, but is it > possible to short-circuit those definitions in the stdio.h header with > some macro definition? And would that make the execution succeed? If I modify stdio.h to #if 0 the definitions, then at least 16 fprintf tests pass (that's the only one I modified). We don't currently provide a macro mechanism to disable these, though. @jon_y, is this a reasonable workaround? (Ideally, fixing the test would happen instead, but if it's desirable that the headers can optionally define *printf outside of the testsuite, then we should entertain that as well).
