NOTE! Perl is not -fsanitize=undefined clean, so any failures are unlikely your fault.
Smoke logs available at http://m-l.org/~perl/smoke/perl/linux/smoke-me_clang_quick_sanitize=undefined/Steve%20Hay/logd4afdb4a71482d6f771062dea05056406ebd3766.log.gz Automated smoke report for 5.21.9 patch d4afdb4a71482d6f771062dea05056406ebd3766 v5.21.8-36-gd4afdb4 zwei: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz (GenuineIntel 2668MHz) (x86_64/8 cpu) on linux - 3.16.0-29-generic [debian] using clang version 4.2.1 Compatible Ubuntu Clang 3.5.0 (tags/RELEASE_350/final) smoketime 6 hours 52 minutes (average 1 hour 43 minutes) Summary: FAIL(m) O = OK F = Failure(s), extended report at the bottom X = Failure(s) under TEST but not under harness ? = still running or test results not (yet) available Build failures during: - = unknown or N/A c = Configure, m = make, M = make (after miniperl), t = make test-prep v5.21.8-36-gd4afdb4 Configuration (common) -Accflags="-DPERL_POISON -Werror=declaration-after-statement -fsanitize=undefined -fsanitize-blacklist=`pwd`/asan_ignore" -Aldflags="-fsanitize=undefined" -Dcc=clang ----------- --------------------------------------------------------- m m m m -Duseithreads | +--------- -DDEBUGGING +----------- no debugging Locally applied patches: SMOKEd4afdb4a71482d6f771062dea05056406ebd3766 Testsuite was run only with 'harness' Compiler messages(gcc): try.c:8030:40: error: __has_include must be used within a preprocessing directive try.c:8042:45: error: __has_include_next must be used within a preprocessing directive -- Report by Test::Smoke v1.53 build 1374 running on perl 5.20.1 (Reporter v0.050 / Smoker v0.045)
