[Hexagon][CI] Updated sha for builder LLVM

[joshherr-quic]

Updated sha to deal with some codegen issues that came up with the last version.

[tvm-bot]

Thanks for contributing to TVM! Please refer to the contributing guidelines https://tvm.apache.org/docs/contribute/ for useful information and tips. Please request code reviews from Reviewers by @-ing them in a comment.

• cc @Icemist, @Mousius, @areusch, @driazati, @gigiblender, @ibsidorenko, @leandron, @mehrdadh, @quic-sanirudh _{See #10317 for details}
• Built docs for commit 75a9bbc can be found here.

_{Generated by tvm-bot}

[mehrdadh]

@joshherr-quic thanks for the PR! Could you please build the docker locally and run hexagon tests with the simulator?

[joshherr-quic]

@joshherr-quic thanks for the PR! Could you please build the docker locally and run hexagon tests with the simulator?

Will do. Is there a wiki with some quick instructions on how to do this?

Edit: Figured it out

[ibsidorenko]

Hi, @mehrdadh and @joshherr-quic !
Sorry for stupid question, but when I try to use Hexagon docker I run the following command:
./docker/bash.sh ci_hexagon
But as I see from the downloaded image it still uses LLVM-14:

$ /opt/clang-llvm/bin/llvm-config --version
14.0.0

But even LLVM_SHA=361a27c155ec8b should correspond to LLVM-15.x if I am correct.

What should I do to use up-to-date LLVM version in the docker image? Build the docker locally?

[joshherr-quic]

Hi, @mehrdadh and @joshherr-quic ! Sorry for stupid question, but when I try to use Hexagon docker I run the following command: ./docker/bash.sh ci_hexagon But as I see from the downloaded image it still uses LLVM-14:

$ /opt/clang-llvm/bin/llvm-config --version
14.0.0

But even LLVM_SHA=361a27c155ec8b should correspond to LLVM-15.x if I am correct.

What should I do to use up-to-date LLVM version in the docker image? Build the docker locally?

The docker image you download is built according to the tvm commit that corresponds to this commit id. That commit still has llvm 14. The PR that we're looking at merely updates the docker image that would get built locally. We still need to open another PR to update the commit id in the Jenkinsfile so that CI will build the new LLVM version. Only after that follow-up commit will the updated docker with the newer llvm be available.

So your intuition is correct! You would need to build the docker locally to take advantage of the newest LLVM right now. New dockers with new llvm should hopefully be available over the weekend for download.

[mehrdadh]

waiting for passing test confirmation

Hexagon tests need to be run first

[mehrdadh]

@ibsidorenko so after @joshherr-quic confirms the tests are passing, we will merge this PR and update the docker image. In the meantime if you need to use docker with updated LLVM, you need to build it locally. We also have automated nightly image build which is published here: https://hub.docker.com/r/tlcpackstaging/ci_hexagon/tags. These docker images are built based on the most recent commit, so the last one should have updated LLVM
These images are not necessarily usable because some of them are failing on some tests

[joshherr-quic]

I'm seeing a lot of "AttributeError: 'HexagonLauncherSimulator' object has no attribute '_se" errors, but nothing related to codegen...

[mehrdadh]

@joshherr-quic where do you see those errors? can you post them here?

[mehrdadh]

@joshherr-quic any update on this?
Unfortunately This is blocking updating hexagon image. I appreciate if you could provide a follow up on this. thanks!

[mehrdadh]

cc @kparzysz-quic

[kparzysz-quic]

The CI tests have passed with a docker image built from this.