Errors that occur when reading an MRI script would be clearer if they included a corresponding line number.
Details
- Reviewers
rupprecht MaskRay grimar jhenderson - Commits
- rG25040f8dec2e: Reapply [llvm-ar] Include a line number when failing to parse an MRI script
rL372374: Reapply [llvm-ar] Include a line number when failing to parse an MRI script
rL372311: Revert [llvm-ar] Include a line number when failing to parse an MRI script
rGaa03c14827fa: Revert [llvm-ar] Include a line number when failing to parse an MRI script
rG04398c729b20: [llvm-ar] Include a line number when failing to parse an MRI script
rL372309: [llvm-ar] Include a line number when failing to parse an MRI script
Diff Detail
Event Timeline
I wish we can create a new function for MRI error reporting but as it stands, runMRIScript can call readLibrary, addChildMember, and addMember which can in turn call fail or failIfError, so fail has to be aware of the MRI line number. +@grimar @jhenderson in case they have suggestions.
llvm/test/tools/llvm-ar/mri-errors.test | ||
---|---|---|
10 | A bit inconvenience for you (sorry!): after D67558, the error messages are no longer capitalized, so this needs a rebase. If I recall correctly, one point raised by @grimar or @jhenderson before is that we should still use # comment markers even if the test contains no code. I hope they can confirm. |
llvm/test/tools/llvm-ar/mri-errors.test | ||
---|---|---|
10 | Well, I also do not remember now, but I would be happy to see ## as a comment marker everywhere in tests, |
The only suggestion I have is to pass in an error handler from the calling code that can be used to generate an Error instance with a message customised to the caller. Default would be to do nothing special of course, but it would allow the MRI parser to pass one that refers back to a handler that appends the line number. That's potentially quite a significant refactor, so might be worth delaying to a subsequent change, but it might also be worth being done before this, so that we don't have to introduce the if statement in fail. What do people think?
llvm/test/tools/llvm-ar/mri-errors.test | ||
---|---|---|
2 | Nit: white space -> whitespace | |
10 | I have no strong preference for # versus ##, as long as we use one in tests which don't necessarily need them, as it makes the comments stand-out from the rest of the test (same reason for using ## in tests that need # for RUN lines etc). If someone else has a preference to use ## everywhere, that's fine with me. |
I am not good familar with this tool's code yet, but at first look introducing a custom handler looks reasonable (that would help to remove most of these new variables it seems).
llvm/tools/llvm-ar/llvm-ar.cpp | ||
---|---|---|
1042 | Is there any reason to check Saved? Can it be just like the following? ParsingMRIScript = false; // Nothing to do if not saved. if (Saved) performOperation(ReplaceOrInsert, &NewMembers); |
I am not sure though. The current approach is simple and I do not know/see for what else such handler can be usefull here. So I'd just go with this patch for now probably.
llvm/test/tools/llvm-ar/mri-errors.test | ||
---|---|---|
10 | Just to make the action item concrete, Test different ... -> ## Test different ... |
Thanks for all the feedback. Regarding an error handler I think the introduction of an error handler could be left for another time.
Nit: white space -> whitespace