LLVM codebase has generated files (all are build/Target/XXX/*.inc) that
exceed the MaxLine & MaxColumn. Printing these log would be noisy.
Details
Details
Diff Detail
Diff Detail
- Repository
- rCTE Clang Tools Extra
- Build Status
Buildable 23904 Build 23903: arc lint + arc unit
Event Timeline
Comment Actions
After looking at the examples, I'm reassured that we don't really care about tracking precise locations of those references :-)
I'd suggest adding the logging just to where the field is *read* in XRefs.cpp (check if it's max-value).
That would cover a bunch of the cases where an incorrect location is likely to be visible.
Comment Actions
Some nitty ideas about the log message, but whatever you think is best.
clangd/XRefs.cpp | ||
---|---|---|
43 | Log message could use more context. And I think it'd be really useful to print the whole location here. bikeshed: you could add a method bool Position::hasOverflow(), and then write below if (LSPLoc.range.start.hasOverflow() || LSPLoc.range.end.hasOverflow()) log("Possible overflow in symbol location: {0}", LSPLoc); Distinguishing between line/column overflow isn't important if you're printing the full range anyway. |
clangd/XRefs.cpp | ||
---|---|---|
43 | This is neat. |
Log message could use more context. And I think it'd be really useful to print the whole location here.
bikeshed: you could add a method bool Position::hasOverflow(), and then write below
Distinguishing between line/column overflow isn't important if you're printing the full range anyway.