[lld,test] fix few filecheck annotation typos

[klensy]

Plus few places where i don't know how to resolve issues:

llvm-project/lld/test/MachO/export-options.s

Lines 200 to 204 in f39e75b

	# REEXPORT: Exports trie:
	# REEXPORT-NEXT: [re-export] _tlv [per-thread] (from libdefault)
	# REEXPORT-NEXT: [re-export] _keep_globl (from libdefault)
	# REEXPORT-NEXT: [re-export] _undef (from unknown)

unknown prefix

llvm-project/lld/test/MachO/export-options.s

Line 211 in f39e75b

# RUN: --check-prefix=EMPTY-TRIE

unused prefix

https://github.com/llvm/llvm-project/blame/421862f8e4ffddf57e210a205984a0ee39c57d96/lld/test/ELF/riscv-gp.s#L19-L21 unknown prefix

https://github.com/llvm/llvm-project/blame/421862f8e4ffddf57e210a205984a0ee39c57d96/lld/test/ELF/ppc64-reloc-addr.s#L9 unkown prefix HEXBE
https://github.com/llvm/llvm-project/blame/421862f8e4ffddf57e210a205984a0ee39c57d96/lld/test/ELF/ppc64-toc-relax-ifunc.s#L24-L26 unknown prefox REL
https://github.com/llvm/llvm-project/blame/main/lld/test/ELF/ppc64-pcrel-call-to-extern.s unknown prefixes 'SEC-OG', 'REL-NEXT-OG'
https://github.com/llvm/llvm-project/blame/421862f8e4ffddf57e210a205984a0ee39c57d96/lld/test/ELF/ppc32-reloc-rel.s#L25-L26 unknown prefix HEX
https://github.com/llvm/llvm-project/blame/d187005cad8c2cb7d44ba3dd6b01c5f0e4c14ae7/lld/test/ELF/mips-tls-hilo.s#L31-L39 unknown prefix SO
https://github.com/llvm/llvm-project/blame/main/lld/test/ELF/arm-exidx-shared.s prefix uses filecheck command as part of name: CHECK-EXTAB-NEXT, ambiguity

[github-actions]

Thank you for submitting a Pull Request (PR) to the LLVM Project!

This PR will be automatically labeled and the relevant teams will be
notified.

If you wish to, you can add reviewers by using the "Reviewers" section on this page.

If this is not working for you, it is probably because you do not have write
permissions for the repository. In which case you can instead tag reviewers by
name in a comment by using @ followed by their GitHub username.

If you have received no comments on your PR for a week, you can request a review
by "ping"ing the PR by adding a comment “Ping”. The common courtesy "ping" rate
is once a week. Please remember that you are asking for valuable time from other developers.

If you have further questions, they may be answered by the LLVM GitHub User Guide.

You can also ask questions in a comment on this PR, on the LLVM Discord or on the forums.

[llvmbot]

@llvm/pr-subscribers-lld-macho

@llvm/pr-subscribers-lld

Author: klensy (klensy)

Changes

Plus few places where i don't know how to resolve issues:

llvm-project/lld/test/MachO/export-options.s

Lines 200 to 204 in f39e75b

	# REEXPORT: Exports trie:
	# REEXPORT-NEXT: [re-export] _tlv [per-thread] (from libdefault)
	# REEXPORT-NEXT: [re-export] _keep_globl (from libdefault)
	# REEXPORT-NEXT: [re-export] _undef (from unknown)

unknown prefix

llvm-project/lld/test/MachO/export-options.s

Line 211 in f39e75b

# RUN: --check-prefix=EMPTY-TRIE

unused prefix

https://github.com/llvm/llvm-project/blame/421862f8e4ffddf57e210a205984a0ee39c57d96/lld/test/ELF/riscv-gp.s#L19-L21 unknown prefix

https://github.com/llvm/llvm-project/blame/421862f8e4ffddf57e210a205984a0ee39c57d96/lld/test/ELF/ppc64-reloc-addr.s#L9 unkown prefix HEXBE
https://github.com/llvm/llvm-project/blame/421862f8e4ffddf57e210a205984a0ee39c57d96/lld/test/ELF/ppc64-toc-relax-ifunc.s#L24-L26 unknown prefox REL
https://github.com/llvm/llvm-project/blame/main/lld/test/ELF/ppc64-pcrel-call-to-extern.s unknown prefixes 'SEC-OG', 'REL-NEXT-OG'
https://github.com/llvm/llvm-project/blame/421862f8e4ffddf57e210a205984a0ee39c57d96/lld/test/ELF/ppc32-reloc-rel.s#L25-L26 unknown prefix HEX
https://github.com/llvm/llvm-project/blame/d187005cad8c2cb7d44ba3dd6b01c5f0e4c14ae7/lld/test/ELF/mips-tls-hilo.s#L31-L39 unknown prefix SO
https://github.com/llvm/llvm-project/blame/main/lld/test/ELF/arm-exidx-shared.s prefix uses filecheck command as part of name: CHECK-EXTAB-NEXT, ambiguity

---

Full diff: https://github.com/llvm/llvm-project/pull/92238.diff

2 Files Affected:

• (modified) lld/test/MachO/install-name.s (+1-1)
• (modified) lld/test/MachO/objc-methname.s (+1-1)

diff --git a/lld/test/MachO/install-name.s b/lld/test/MachO/install-name.s
index 1cf675e278bfa..c419c6ca1f951 100644
--- a/lld/test/MachO/install-name.s
+++ b/lld/test/MachO/install-name.s
@@ -31,7 +31,7 @@
 
 # ID:          cmd LC_ID_DYLIB
 # ID-NEXT: cmdsize
-# LID-NEXT:   name foo
+# ID-NEXT:   name foo
 
 .globl _main
 _main:
diff --git a/lld/test/MachO/objc-methname.s b/lld/test/MachO/objc-methname.s
index afc137eac8c21..3d06472971c80 100644
--- a/lld/test/MachO/objc-methname.s
+++ b/lld/test/MachO/objc-methname.s
@@ -16,7 +16,7 @@
 
 # CSTRING: Contents of (__TEXT,__cstring) section
 # CSTRING-NEXT: existing-cstring
-# CSTIRNG-EMPTY:
+# CSTRING-EMPTY:
 
 # METHNAME: Contents of (__TEXT,__objc_methname) section
 # METHNAME-NEXT: existing_methname

[github-actions]

@klensy Congratulations on having your first Pull Request (PR) merged into the LLVM Project!

Your changes will be combined with recent changes from other authors, then tested
by our build bots. If there is a problem with a build, you may receive a report in an email or a comment on this PR.

Please check whether problems have been caused by your change specifically, as
the builds can include changes from many authors. It is not uncommon for your
change to be included in a build that fails due to someone else's changes, or
infrastructure issues.

How to do this, and the rest of the post-merge process, is covered in detail here.

If your change does cause a problem, it may be reverted, or you can revert it yourself.
This is a normal part of LLVM development. You can fix your changes and open a new PR to merge them again.

If you don't get any reports, no action is required from you. Your changes are working as expected, well done!

[MaskRay]

I merged this PR before I realized that you are using a users.noreply.github.com email address.

Note: the consensus is to avoid them: https://discourse.llvm.org/t/hidden-emails-on-github-should-we-do-something-about-it/74223/32

[MaskRay]

Plus few places where i don't know how to resolve issues:

Thanks for these links. I'll try fixing them.