diff options
| author | Martin Storsjö <martin@martin.st> | 2023-10-25 14:38:30 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-10-25 14:38:30 +0300 |
| commit | 6d66440c50e3047b5ce152830d4ccae381c7c2bf (patch) | |
| tree | 7c55047a9f112087b7af9a2cad94d6f2b29e0736 /clang/unittests/Format/ConfigParseTest.cpp | |
| parent | c4e9a4377398a22e38cafe72f2793681b55c5bb1 (diff) | |
| download | llvm-6d66440c50e3047b5ce152830d4ccae381c7c2bf.zip llvm-6d66440c50e3047b5ce152830d4ccae381c7c2bf.tar.gz llvm-6d66440c50e3047b5ce152830d4ccae381c7c2bf.tar.bz2 | |
[LLD] [MinGW] Hook up --icf=safe to -opt:safeicf (#70037)
Back when the --icf= option was hooked up in the MinGW frontend in LLD,
in 2017, lld-link didn't support safe ICF, and mapping it to noicf was
suggested in review: https://reviews.llvm.org/D40019
In 2018, in ab038025a50c79a89edb5832b163e8c729ceb703,
lld-link did get support for handling address significance tables,
allowing the ICF to operate safely on more sections.
Later in 2021, lld-link did get support for a separate safe ICF mode in
5bdc5e7efda4100c4d11085c2da8f1fb932ccce4 /
https://reviews.llvm.org/D97436.
Hook this up for the MinGW frontend as well.
Diffstat (limited to 'clang/unittests/Format/ConfigParseTest.cpp')
0 files changed, 0 insertions, 0 deletions