GNU binutils nm doesn't error out on this, and some projects' build systems can end up doing that in some cases. Allowing that seems like a better target than trying to avoid user projects passing multiple -g parameters to $NM.
Details
Details
Diff Detail
Diff Detail
- Repository
- rL LLVM
Event Timeline
Comment Actions
I'm not super familiar with the option parser by any means, but I think changing specific flags to be ZeroOrMore rather than Optional is much better than doing a global change for the behavior of Optional.
Comment Actions
Agreed. Optional should basically be called OneOrZero. And if you think about it in those terms, it obviously doesn't make sense to allow it to be specified more than once.
Just change this specific option to be ZeroOrMore