[all-commits] [llvm/llvm-project] 73bcac: [llvm-objdump][MachO] Update check in flaky test t...

[Akshay Deodhar via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 73bcac28d0bfbfd8c997385f25637b85c8f0f818
      https://github.com/llvm/llvm-project/commit/73bcac28d0bfbfd8c997385f25637b85c8f0f818
  Author: Akshay Deodhar <adeodhar at nvidia.com>
  Date:   2025-09-25 (Thu, 25 Sep 2025)

  Changed paths:
    M llvm/test/tools/llvm-objdump/MachO/function-starts.test

  Log Message:
  -----------
  [llvm-objdump][MachO] Update check in flaky test that depends on directory path (#150674)

Earlier, function-starts.test failed when directory path contained
'_main', because objdump prints out the entire directory path, and there
is an implicit-check-not for '_main'.
There's three ways in which [function starts are printed by
llvm-objdump](https://llvm.org/docs/CommandGuide/llvm-objdump.html#cmdoption-llvm-objdump-function-starts): 

With the "addr" mode, there will be no "_main"\
With "names", it'll be printed as "_main\n"\
With "both", it'll be printed as "<addr> _main\n". 

The existing check for function-starts=addrs checks that the pattern for
"names" or "both" does not get printed. This MR changes the RUN lines to
take stdin input, so that no directory path is printed, and stray _main
strings in the directory path will not make the test fail.



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications