Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Yes, this looks reasonable. The additional warning is somewhat unfortunate, and we could avoid it, but at the same time i don't expect it would bother anyone given how unlikely the scenario is to begin with.
Thanks for fixing that!
Thanks! I believe it fixes a long tail crash.
clang/unittests/Lex/LexerTest.cpp | ||
---|---|---|
665 | nit: I'd probably use a clang lit test auto nocrash = L"\N"; but up to you. |
clang/unittests/Lex/LexerTest.cpp | ||
---|---|---|
665 | Nah, this test is good. It could only crash at at the end of a file, which would be flacky at best with lit. |
this is causing some crashes in buildbots, and i can't repro. reverting until i figure this out.
i'll reland the fix without the test case, as it's clearly fixing one of the codepaths that'll lead to a crash. it's only the test case that's crashing, because i don't think there are certain test cases that exposed literal parser to invalid/incomplete input and i am not able to reproduce any of the crashes i've seen in buildbots locally (even under asan/msan) and because the bots don't have stack traces for whatever reason, it's impossible to chase from my side. i've pinged buildbot owners in https://discourse.llvm.org/t/buildbots-missing-stack-traces/65753 to see the issue fixed.
Makes sense. The fix is correct and if it wasn't it would affect all bots equally (I highly doubt that code path is exercised anywhere but the lex test)
nit: I'd probably use a clang lit test
but up to you.