- User Since
- Oct 27 2019, 11:03 AM (36 w, 1 d)
May 31 2020
It looks like clang/test/Profile/Inputs/c-general.profdata.v5 is being read as v6 rather than v5. Can you double check?
May 28 2020
clang/test/CodeGen/sanitize-coverage.c is also failing our downstream embedded ARMv7 validations.
Jan 21 2020
This test is still failing on the arm bots and also with my downstream ARM compiler validation.
Jan 17 2020
Hello! Your test specifically looks for "248", which is failing with my downstream embedded ARM compiler (we produce "249"); other similar tests that I've looked at simply ignore this value. Is there a reason why you need to check it specifically?
Jan 10 2020
Sorry, we just saw your commit to fix. We are OK. Thanks!
We maintain a downstream embedded ARM compiler, and this test is failing for us now because it assumes a 64bit size_t in the first CHECK line of the mempcpy-libcall.c. Because this is testing a GNU specific builtin, should it be specific to only targets that support that? Or should it be extended to support 32bit size_t?