From: Mehdi Amini Date: Fri, 10 Feb 2017 07:21:06 +0000 (+0000) Subject: Fix doc for `-opt-bisect-limit`: the LTO option is linker specific X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=2fabd44db6dbabd8390680ffdf77457c52bcd718;p=llvm Fix doc for `-opt-bisect-limit`: the LTO option is linker specific git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@294725 91177308-0d34-0410-b5e6-96231b3b80d8 --- diff --git a/docs/OptBisect.rst b/docs/OptBisect.rst index e9f1c2541c9..a9ac227a2af 100644 --- a/docs/OptBisect.rst +++ b/docs/OptBisect.rst @@ -60,12 +60,15 @@ like this: clang -O2 -mllvm -opt-bisect-limit=256 my_file.c The -opt-bisect-limit option may also be applied to link-time optimizations by -using a prefix to indicate that this is a plug-in option for the linker. The +using a prefix to indicate that this is a plug-in option for the linker. The 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) + clang -flto -Wl,-mllvm,-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