[llvm] r294725 - Fix doc for `-opt-bisect-limit`: the LTO option is linker specific
Mehdi Amini via llvm-commits
llvm-commits at lists.llvm.org
Thu Feb 9 23:21:07 PST 2017
Author: mehdi_amini
Date: Fri Feb 10 01:21:06 2017
New Revision: 294725
URL: http://llvm.org/viewvc/llvm-project?rev=294725&view=rev
Log:
Fix doc for `-opt-bisect-limit`: the LTO option is linker specific
Modified:
llvm/trunk/docs/OptBisect.rst
Modified: llvm/trunk/docs/OptBisect.rst
URL: http://llvm.org/viewvc/llvm-project/llvm/trunk/docs/OptBisect.rst?rev=294725&r1=294724&r2=294725&view=diff
==============================================================================
--- llvm/trunk/docs/OptBisect.rst (original)
+++ llvm/trunk/docs/OptBisect.rst Fri Feb 10 01:21:06 2017
@@ -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
More information about the llvm-commits
mailing list