Switch to OptParser for command-line handling
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Nice!
Do tests still run after the test file renaming to .asm? llvm/test/lit.cfg.py has config.suffixes = ['.ll', '.c', '.test', '.txt', '.s', '.mir', '.yaml'] which includes .test but not .asm. I would expect that you need to edit llvm/test/tools/llvm-ml/lit.local.cfg to have config.suffixes.add('.asm,') for the tests to keep running.
llvm/tools/llvm-ml/Opts.td | ||
---|---|---|
7 | Do we need the non-ml-compat options for anything? If so, why support '/' prefixes for this? Why not the more usual '--' here? (see also lld/ELF/Options.td for some color on this.) What's with the '.' syntax? |
(marking this as "request changes" to get it off my dashboard until the questions above are answered. doesn't necessarily need changes, more "request replies" :) )
... they do now. Thanks for catching this! (They still pass.)
llvm/tools/llvm-ml/Opts.td | ||
---|---|---|
7 | We do need it for now - it lets users select things like output filetype. (We might be able to replace that with the listing options once those are implemented, and generally I plan on working to converge towards ML.EXE's interface.) I've switched to supporting only "-" and "--" here; I'm keeping "-" available for partial compatibility with llvm-mc. (And the "." was a typo.) |
Yep - working on getting it in, at a not-quite-top priority at the moment. It was blocked the other day behind an intermediate change.
Do we need the non-ml-compat options for anything? If so, why support '/' prefixes for this? Why not the more usual '--' here? (see also lld/ELF/Options.td for some color on this.)
What's with the '.' syntax?