diff options
| author | Joseph Huber <huberjn@outlook.com> | 2024-10-29 13:06:55 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-10-29 13:06:55 -0700 |
| commit | ccd73eeab34b31c7c38e9aca05ca4192fb0913b0 (patch) | |
| tree | b358682fa3d7185a82e8686ff736166a8b23b22d /llvm/lib | |
| parent | ba8d9ce8d4f0665f29bb4bb43ce16d02acaed751 (diff) | |
| download | llvm-ccd73eeab34b31c7c38e9aca05ca4192fb0913b0.zip llvm-ccd73eeab34b31c7c38e9aca05ca4192fb0913b0.tar.gz llvm-ccd73eeab34b31c7c38e9aca05ca4192fb0913b0.tar.bz2 | |
[LinkerWrapper] Remove in-house handling of LTO (#113715)
Summary:
This should be the linker's job if the user creates any bitcode files,
then passing `-flto` to the linker for the toolchain should be able to
handle it. Right now this path is only used in the case where someone
does LTO w/ ld.gold targeting a CPU so I think we are safe here as that
will still be forwarded, for bfd it'll be an error as it would on the
host. I think I talked the SYCL team out of using this as well so I
should be good to delete it.
Diffstat (limited to 'llvm/lib')
0 files changed, 0 insertions, 0 deletions