Skip to content

Conversation

XeniaLu
Copy link
Contributor

@XeniaLu XeniaLu commented Oct 3, 2025

See also: referenced LLVM pull requests in patch files.

See also: referenced LLVM pull requests in patch files.
@XeniaLu XeniaLu force-pushed the build-llvm-on-gcc-15 branch from b248637 to 039dd17 Compare October 3, 2025 02:29
@lum1n0us
Copy link
Collaborator

Is this due to some compilation errors raised by GCC 15(or higher only)? Do lower versions of GCC, like GCC 11, encounter the same issues under specific conditions?

@XeniaLu
Copy link
Contributor Author

XeniaLu commented Oct 12, 2025

It's only happening on GCC 15 (and higher, and potentially some corresponding versions of clang): llvm/llvm-project#101761 and llvm/llvm-project#123320

@lum1n0us
Copy link
Collaborator

Will lower versions of GCC, like GCC 11 (default on Ubuntu 22.04), successfully compile LLVM libraries after applying those (llvm) patches?

@XeniaLu
Copy link
Contributor Author

XeniaLu commented Oct 15, 2025

Yes, it builds on Ubuntu 22.04 (GCC 11) with the same patches.

print(f"cd {dst_dir} && {GIT_CLONE_CMD}")
subprocess.check_output(shlex.split(GIT_CLONE_CMD), cwd=dst_dir)

patch_dir = pathlib.Path(__file__).parent.joinpath("llvm-patches").resolve()
Copy link
Collaborator

Choose a reason for hiding this comment

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

i suspect this should be target dependent.

while we are currently using the similar version (llvm-18) for all targets, it has not always been the case.
and it will unlikely be the case in future.
cf. #4654

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.

3 participants