Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[LoongArch] Switch the toolchain used by the clang-loongarch64-linux builder from default to clang+lld #193

Merged
merged 1 commit into from
May 18, 2024

Conversation

SixWeining
Copy link
Contributor

Currently the default toolchain is used:

  • gcc (GCC) 13.0.0 20221013 (experimental)
  • GNU ld (GNU Binutils) 2.39.50.20221029

But recently we find that a new added llvm unittest (llvm/unittests/Frontend/OpenMPDecompositionTest.cpp) can't be compiled by the default toolchain (causing memory exhausted and killed by the system). Error:

command timed out: 1200 seconds without output running [b'ninja', b'check-all'], attempting to kill
process killed by signal 9
program finished with exit code -1
elapsedTime=1669.062469

See https://lab.llvm.org/staging/#/builders/5/builds/4199.

This patch fixex this issue by switching to clang+lld (v17.0.6).

An alternative (workaround) is setting useTwoStage=True and testStage1=False, but I think we'd better to create a dedicated builder for that in future.

…` builder from default to clang+lld

Currently the default toolchain is used:
- gcc (GCC) 13.0.0 20221013 (experimental)
- GNU ld (GNU Binutils) 2.39.50.20221029

But recently we find that a new added llvm unittest
(llvm/unittests/Frontend/OpenMPDecompositionTest.cpp) can't be
compiled by the default toolchain (causing memory exhausted and killed
by the system). Error:
```
command timed out: 1200 seconds without output running [b'ninja', b'check-all'], attempting to kill
process killed by signal 9
program finished with exit code -1
elapsedTime=1669.062469
```
See https://lab.llvm.org/staging/#/builders/5/builds/4199.

This patch fixex this issue by switching to clang+lld (v17.0.6).

An alternative (workaround) is setting `useTwoStage=True` and
`testStage1=False`, but I think we'd better to create a dedicated
builder for that in future.
Copy link
Contributor

@gkistanova gkistanova left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

@SixWeining SixWeining merged commit 7c995dc into llvm:main May 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants