From a826244bb1ec67610a2c071c79e6c9dcf2d6e68e Mon Sep 17 00:00:00 2001 From: Mehdi Amini Date: Fri, 10 Feb 2017 07:21:06 +0000 Subject: [PATCH] Fix doc for `-opt-bisect-limit`: the LTO option is linker specific llvm-svn: 294725 --- llvm/docs/OptBisect.rst | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/llvm/docs/OptBisect.rst b/llvm/docs/OptBisect.rst index e9f1c2541c9c..a9ac227a2af5 100644 --- a/llvm/docs/OptBisect.rst +++ b/llvm/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