-o is very common among tools. yaml2obj supports -o and it surprised me that
obj2yaml doesn't support -o. Just add it which doesn't take much code.
Details
- Reviewers
jhenderson - Commits
- rGcfec2080b7a6: [obj2yaml] Add -o to specify output filename
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
llvm/test/tools/obj2yaml/Archives/regular.yaml | ||
---|---|---|
11–13 | I wonder if we could avoid some test duplication in these test cases by doing the following pattern instead: # RUN: obj2yaml %t.empty.a > %t.stdout.yaml # RUN: obj2yaml %t.empty.a -o %t.file.yaml 2>&1 | count 0 # RUN: FileCheck --input-file=%t.stdout.yaml %s --check-prefix=EMPTY # RUN: diff %t.stdout.yaml %t.file.yaml What do you think? The same sort of pattern could apply to the other test cases too. | |
llvm/tools/obj2yaml/obj2yaml.cpp | ||
64 | I guess there isn't an appropriate offloading test case you could update like you have with the others? | |
114 | Should we have a test case that if there was an error, the output file is not kept? It seems like a simple extension to me. |
address comments
llvm/tools/obj2yaml/obj2yaml.cpp | ||
---|---|---|
64 | Found a suitable test: updated llvm/test/ObjectYAML/Offload/default.yaml |
I wonder if we could avoid some test duplication in these test cases by doing the following pattern instead:
What do you think?
The same sort of pattern could apply to the other test cases too.