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

[Docs] Modernize references to macOS

Browse Source 
Summary:
This updates all places in documentation that refer to "Mac OS X", "OS X", etc.
to instead use the modern name "macOS" when no specific version number is
mentioned.

If a specific version is mentioned, this attempts to use the OS name at the time
of that version:

* Mac OS X for 10.0 - 10.7
* OS X for 10.8 - 10.11
* macOS for 10.12 - present

Reviewers: JDevlieghere

Subscribers: mgorny, christof, arphaman, cfe-commits, lldb-commits, libcxx-commits, llvm-commits

Tags: #clang, #lldb, #libc, #llvm

Differential Revision: https://reviews.llvm.org/D62654

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@362113 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
J. Ryan Stinnett 2019-05-30 16:46:22 +00:00
parent 618cbae770
commit 78762bc380
8 changed files with 14 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/CMake.rst
View File

@ -533,7 +533,7 @@ LLVM-specific variables
`share/doc/llvm/ocaml-html`.
**LLVM_CREATE_XCODE_TOOLCHAIN**:BOOL
OS X Only: If enabled CMake will generate a target named
macOS Only: If enabled CMake will generate a target named
'install-xcode-toolchain'. This target will create a directory at
$CMAKE_INSTALL_PREFIX/Toolchains containing an xctoolchain directory which can
be used to override the default system tools.

4
docs/CommandGuide/llvm-ar.rst
View File

@ -229,7 +229,7 @@ STANDARDS
The **llvm-ar** utility is intended to provide a superset of the IEEE Std 1003.2
(POSIX.2) functionality for ``ar``. **llvm-ar** can read both SVR4 and BSD4.4 (or
Mac OS X) archives. If the ``f`` modifier is given to the ``x`` or ``r`` operations
macOS) archives. If the ``f`` modifier is given to the ``x`` or ``r`` operations
then **llvm-ar** will write SVR4 compatible archives. Without this modifier,
**llvm-ar** will write BSD4.4 compatible archives that have long names
immediately after the header and indicated using the "#1/ddd" notation for the
@ -240,7 +240,7 @@ FILE FORMAT
-----------
The file format for LLVM Archive files is similar to that of BSD 4.4 or Mac OSX
The file format for LLVM Archive files is similar to that of BSD 4.4 or macOS
archive files. In fact, except for the symbol table, the ``ar`` commands on those
operating systems should be able to read LLVM archive files. The details of the
file format follow.

4
docs/CompilerWriterInfo.rst
View File

@ -140,8 +140,8 @@ Linux
* `ELF for the ARM 64-bit Architecture (AArch64) <http://infocenter.arm.com/help/topic/com.arm.doc.ihi0056a/IHI0056A_aaelf64.pdf>`_
* `System z ELF ABI Supplement <http://legacy.redhat.com/pub/redhat/linux/7.1/es/os/s390x/doc/lzsabi0.pdf>`_
OS X
----
macOS
-----
* `Mach-O Runtime Architecture <http://developer.apple.com/documentation/Darwin/RuntimeArchitecture-date.html>`_
* `Notes on Mach-O ABI <http://www.unsanity.org/archives/000044.php>`_

2
docs/DebuggingJITedCode.rst
View File

@ -29,7 +29,7 @@ GDB Version
In order to debug code JIT-ed by LLVM, you need GDB 7.0 or newer, which is
available on most modern distributions of Linux. The version of GDB that
Apple ships with Xcode has been frozen at 6.3 for a while. LLDB may be a
better option for debugging JIT-ed code on Mac OS X.
better option for debugging JIT-ed code on macOS.
Debugging MCJIT-ed code

8
docs/GettingStarted.rst
View File

@ -128,8 +128,8 @@ FreeBSD x86\ :sup:`1` GCC, Clang
FreeBSD amd64 GCC, Clang
NetBSD x86\ :sup:`1` GCC, Clang
NetBSD amd64 GCC, Clang
MacOS X\ :sup:`2` PowerPC GCC
MacOS X x86 GCC, Clang
macOS\ :sup:`2` PowerPC GCC
macOS x86 GCC, Clang
Cygwin/Win32 x86\ :sup:`1, 3` GCC
Windows x86\ :sup:`1` Visual Studio
Windows x64 x86-64 Visual Studio
@ -272,7 +272,7 @@ newer version of Gold.
Getting a Modern Host C++ Toolchain
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This section mostly applies to Linux and older BSDs. On Mac OS X, you should
This section mostly applies to Linux and older BSDs. On macOS, you should
have a sufficiently modern Xcode, or you will likely need to upgrade until you
do. Windows does not have a "system compiler", so you must install either Visual
Studio 2015 or a recent version of mingw64. FreeBSD 10.0 and newer have a modern
@ -711,7 +711,7 @@ define compiler flags and variables used during the CMake test operations.
The result of such a build is executables that are not runnable on the build
host but can be executed on the target. As an example the following CMake
invocation can generate build files targeting iOS. This will work on Mac OS X
invocation can generate build files targeting iOS. This will work on macOS
with the latest Xcode:
.. code-block:: console

4
docs/ProgrammersManual.rst
View File

@ -1372,8 +1372,8 @@ these functions in your code in places you want to debug.
Getting this to work requires a small amount of setup. On Unix systems
with X11, install the `graphviz <http://www.graphviz.org>`_ toolkit, and make
sure 'dot' and 'gv' are in your path. If you are running on Mac OS X, download
and install the Mac OS X `Graphviz program
sure 'dot' and 'gv' are in your path. If you are running on macOS, download
and install the macOS `Graphviz program
<http://www.pixelglow.com/graphviz/>`_ and add
``/Applications/Graphviz.app/Contents/MacOS/`` (or wherever you install it) to
your path. The programs need not be present when configuring, building or

2
docs/TestingGuide.rst
View File

@ -511,7 +511,7 @@ RUN lines:
The suffix for the host platforms shared library files. This includes the
period as the first character.
Example: ``.so`` (Linux), ``.dylib`` (OS X), ``.dll`` (Windows)
Example: ``.so`` (Linux), ``.dylib`` (macOS), ``.dll`` (Windows)
``%exeext``
The suffix for the host platforms executable files. This includes the

2
docs/WritingAnLLVMPass.rst
View File

@ -77,7 +77,7 @@ This build script specifies that ``Hello.cpp`` file in the current directory
is to be compiled and linked into a shared object ``$(LEVEL)/lib/LLVMHello.so`` that
can be dynamically loaded by the :program:`opt` tool via its :option:`-load`
option. If your operating system uses a suffix other than ``.so`` (such as
Windows or Mac OS X), the appropriate extension will be used.
Windows or macOS), the appropriate extension will be used.
Now that we have the build scripts set up, we just need to write the code for
the pass itself.