From: Mehdi Amini Date: Fri, 10 Feb 2017 17:16:00 +0000 (+0000) Subject: Fix doc for `-opt-bisect-limit`: the LTO option prefix for lld is -mllvm X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=00b42cc2f1a1c61cd94e12c0c4689d399b2eaed2;p=llvm Fix doc for `-opt-bisect-limit`: the LTO option prefix for lld is -mllvm Thanks Davide to catch it in my previous patch. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@294759 91177308-0d34-0410-b5e6-96231b3b80d8 --- diff --git a/docs/OptBisect.rst b/docs/OptBisect.rst index a9ac227a2af..14eb57bc7d5 100644 --- a/docs/OptBisect.rst +++ b/docs/OptBisect.rst @@ -65,10 +65,10 @@ following syntax will set a bisect limit for LTO transformations: :: - # When using Gold or lld - clang -flto -Wl,-plugin-opt,-opt-bisect-limit=256 my_file.o my_other_file.o - # When using ld64 (macOS) + # When using lld, or ld64 (macOS) clang -flto -Wl,-mllvm,-opt-bisect-limit=256 my_file.o my_other_file.o + # When using Gold + clang -flto -Wl,-plugin-opt,-opt-bisect-limit=256 my_file.o my_other_file.o LTO passes are run by a library instance invoked by the linker. Therefore any passes run in the primary driver compilation phase are not affected by options