RPCS3/llvm
1
0
Fork 0
mirror of https://github.com/RPCS3/llvm.git synced 2024-12-13 14:47:00 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Remove remaining references to -O4.

Browse Source 
Thanks to Hal Finkel for noticing it.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@191216 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Rafael Espindola 2013-09-23 19:50:59 +00:00
parent 670711e662
commit fe8f9e7a03
1 changed files with 2 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/GoldPlugin.rst
View File

@ -66,10 +66,8 @@ look for the line where it runs ``collect2``. Replace that with
ready to switch to using gold, backup your existing ``/usr/bin/ld``
then replace it with ``ld-new``.
You can produce bitcode files from ``clang`` using ``-emit-llvm`` or
``-flto``, or the ``-O4`` flag which is synonymous with ``-O3 -flto``.
Any of these flags will also cause ``clang`` to look for the gold plugin in
You should produce bitcode files from ``clang`` with the option
``-flto``. This flag will also cause ``clang`` to look for the gold plugin in
the ``lib`` directory under its prefix and pass the ``-plugin`` option to
``ld``. It will not look for an alternate linker, which is why you need
gold to be the installed system linker in your path.
@ -153,7 +151,6 @@ everything is in place for an easy to use LTO build of autotooled projects:
export AR="$PREFIX/bin/ar"
export NM="$PREFIX/bin/nm"
export RANLIB=/bin/true #ranlib is not needed, and doesn't support .bc files in .a
export CFLAGS="-O4"
* Or you can just set your path:
@ -163,7 +160,6 @@ everything is in place for an easy to use LTO build of autotooled projects:
export CC="clang -flto"
export CXX="clang++ -flto"
export RANLIB=/bin/true
export CFLAGS="-O4"
* Configure and build the project as usual:
.. code-block:: bash