llvmPackages_git.openmp: apply #197674 (fix cross compile)

[rrbutani]

This was applied to llvmPackages_15 in 81ef82a.

I ended up needing this in #213202 to apply the libclc changes there to llvmPackages_git (like openmp, libclc wants targetLlvm).

Description of changes

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 23.05 Release Notes (or backporting 22.11 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

[RaitoBezarius]

I'm not sure what to test here, I will try:

@ofborg build pkgsCross.aarch64-multiplatform.llvmPackages_git.openmp

[rrbutani]

Hmm looks like the FileCheck JSON error from #222220 is back 🙁.

I'll see if I can reproduce locally.

---

I finally managed to reproduce this locally.

# using `cntr` and `breakpointHook` (set `postCheck` to `exit 4` or something)

cd build/llvm-src-unstable-2022-26-07/llvm/build

# Edit: /var/lib/cntr/build/llvm-src-unstable-2022-26-07/llvm/build/tools/polly/test/lit.site.cfg
# Edit: /var/lib/cntr/build/llvm-src-unstable-2022-26-07/llvm/build/tools/polly/test/Unit/lit.site.cfg
# Edit: /var/lib/cntr/build/llvm-src-unstable-2022-26-07/llvm/build/tools/polly/test/UnitIsl/lit.site.cfg
# Edit: /var/lib/cntr/build/llvm-src-unstable-2022-26-07/llvm/build/utils/lit/lit.site.cfg
# make paths point to `/var/lib/cntr/build`...

python3.10 ./bin/llvm-lit -svj88 --no-progress-bar \
    --param polly_site_config=tools/polly/test/lit.site.cfg \
    --param polly_unit_site_config=tools/polly/test/Unit/lit.site.cfg \
    --param polly_site_config=tools/polly/test/Unit/lit.site.cfg \
    --param polly_site_config=tools/polly/test/UnitIsl/lit.site.cfg \
    tools/polly/test \
    tools/polly/test/Unit \
    tools/polly/test/UnitIsl \
    utils/lit \
    test \
    --filter ScopPassManager

# Running ^ repeatedly is a fast way to reproduce

Sometimes there will be extra lines in gtest produced JSON files; for example, build/tools/polly/unittests/ScopPassManager/ScopPassManagerTests-Polly-Unit-21548-1-3.json:

{
  "tests": 1,
  "failures": 0,
  "disabled": 0,
  "errors": 0,
  "timestamp": "2023-04-10T18:57:23Z",
  "time": "0s",
  "name": "AllTests",
  "testsuites": [
    {
      "name": "ScopPassRegistry",
      "tests": 1,
      "failures": 0,
      "disabled": 0,
      "errors": 0,
      "timestamp": "2023-04-10T18:57:23Z",
      "time": "0s",
      "testsuite": [
        {
          "name": "PrintScopInfo",
          "status": "RUN",
          "result": "COMPLETED",
          "timestamp": "2023-04-10T18:57:23Z",
          "time": "0s",
          "classname": "ScopPassRegistry"
        }
      ]
    }
  ]
}
]
}

(note the two extra lines)

the number of extra lines, contents, etc, are not consistent; sometimes I get:

}
}
  ]
}