clang-13: error: clang frontend command failed with exit code 139 (use -v to see invocation) about proton-clang

[kdrag0n]

This toolchain is bleeding-edge by design and the entire build process is automated. Don't update to every new commit immediately if you need something stable; pick a stable commit and stick to it until you're ready to update.

There are rarely actual compiler issues with anything other than Polly. Breaking changes are not problems with the toolchain, they are intentional changes from upstream LLVM that will make it downstream sooner or later. Using a bleeding-edge toolchain just introduces you to the changes early. This may not be the toolchain for you if you're not willing to deal with that.

[ppajda]

Happend to me too, will try to remove some optimizations and polly from makefile. Maybe that will help.
Edit: removed polly and all is ok now

[dofrancis]

It should be fixed now with this commit, although I could be wrong
llvm/llvm-project@8796451

[Sarisan]

Same here

[redstarksten]

Maybe your source issue. I dont have any problems using latest proton clang commit.

[TogoFire]

Happend to me too, will try to remove some optimizations and polly from makefile. Maybe that will help.
Edit: removed polly and all is ok now

Thx bro.

TogoFire/kernel_xiaomi_panda@98420b2

[Sarisan]

Its intended for compile with polly, so better dont close issue

[TogoFire]

ahh. true

[redstarksten]

Happend to me too, will try to remove some optimizations and polly from makefile. Maybe that will help.
Edit: removed polly and all is ok now

Thx bro.

TogoFire/kernel_xiaomi_panda@5662f3f

The kernel has successful compiled (with CONFIG_LLVM_POLLY=y), but kernel size a little bit smaller. Then when I test to flash the kernel, It wont boot. I did recompile and reflash kernel (using my personal toolchain) just want to make sure that is latest proton clang issue's, the result is, kernel success to boot. So it is confirmed, latest llvm revision using by latest proton clang is the cause of it.

[kdrag0n]

This is now handled properly:

fatal error: error in backend: Option -polly-run-dce not supported with NPM
PLEASE submit a bug report to https://bugs.llvm.org/ and include the crash backtrace, preprocessed source, and associated run script.

Lack of support for Polly dead code elimination in the new optimization pass manager is an upstream LLVM issue. Please submit an upstream bug report if you want it to be added.

[Sarisan]

This is now handled properly:

fatal error: error in backend: Option -polly-run-dce not supported with NPM
PLEASE submit a bug report to https://bugs.llvm.org/ and include the crash backtrace, preprocessed source, and associated run script.

Lack of support for Polly dead code elimination in the new optimization pass manager is an upstream LLVM issue. Please submit an upstream bug report if you want it to be added.

Dude, can you test your clang before release? Its stable only one time of 4 releases.

[kdrag0n]

It should be fixed now with this commit, although I could be wrong
llvm/llvm-project@8796451

Good catch, that should be available in the next build in 3 days.