This unlocks some codepaths in libtool.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
llvm/docs/CommandGuide/llvm-nm.rst needs update.
| llvm/test/tools/llvm-nm/libtool-version.test | ||
|---|---|---|
| 4 | Move the file level comment above the commands. | |
| llvm/tools/llvm-nm/llvm-nm.cpp | ||
| 2241 | Does libtool detect the substring GNU nm? If not, the notice should be dropped. For example, ld.lld prints compatible with GNU linkers just because libtool detects GNU (D31199). | |
| 2241 | If yes, there needs to be a comment. | |
| llvm/tools/llvm-nm/llvm-nm.cpp | ||
|---|---|---|
| 2241 | "llvm-nm, compatible with GNU nm\n" is ok, we just need to document the fact. | |
Looks great! Please wait for @jhenderson
| llvm/test/tools/llvm-nm/libtool-version.test | ||
|---|---|---|
| 7 | Add CHECK: LLVM version (See some similar --version tests) | |
Looks good, with a couple of nits.
| llvm/docs/CommandGuide/llvm-nm.rst | ||
|---|---|---|
| 234–236 | Perhaps change the end of the description here to something like "... executable, then exit." The exiting aspect I think deserves describing, since llvm-nm doesn't need any other commands to still do useful work on an object normally. | |
| llvm/test/tools/llvm-nm/libtool-version.test | ||
| 2–3 | I know they're not strictly necessary here, but I'd add some comment markers to make the comments stand out from the rest of the test. | |
Perhaps change the end of the description here to something like "... executable, then exit." The exiting aspect I think deserves describing, since llvm-nm doesn't need any other commands to still do useful work on an object normally.