-
Notifications
You must be signed in to change notification settings - Fork 13.5k
clang-18: -ffat-lto-objects gives multiple definition of `.str.llvm.0' #84167
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
Comments
cc @ilovepi for fat LTO |
Is this happening at head? I think #83159 should have fixed this. While I didn't run into this for Fuchsia, when trying to enable FatLTO in our Toolchain builds I hit this. Basically the way we set module flags was inconsistent with what we do outside of FatLTO. |
/pull-request #84290 |
@nikic can you prepare the rpm |
@stsp I created a scratch build with this patch: https://koji.fedoraproject.org/koji/taskinfo?taskID=114603529 |
@llvm/issue-subscribers-clang-codegen Author: Stas Sergeev (stsp)
I made the bug reproducer.
Please do the following:
Build process ending with: /usr/bin/ld: /tmp/lto-llvm-00e3b8.o:(.rodata.str1.1+0x70): multiple definition of `.str.2.llvm.0'; /tmp/lto-llvm-98e51f.o:(.rodata.str1.1+0x5b): first defined here Removing -ffat-lto-objects avoids the |
Thanks! |
Awesome, thanks! |
Thanks @nikic I didn't realize we could still backport. |
I made the bug reproducer.
Please do the following:
Build process ending with:
/usr/bin/ld: /tmp/lto-llvm-00e3b8.o:(.rodata.str1.1+0x70): multiple definition of `.str.2.llvm.0'; /tmp/lto-llvm-98e51f.o:(.rodata.str1.1+0x5b): first defined here
Removing -ffat-lto-objects avoids the
problem, but unfortunately rpmbuild
in fedora forces this option.
The text was updated successfully, but these errors were encountered: