maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/libcxxabi/www/index.html

144 lines
5.7 KiB
HTML
Raw Normal View History

initial import llvm-svn: 130921
2011-05-05 23:27:28 +08:00
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<!-- Material used from: HTML 4.01 specs: http://www.w3.org/TR/html401/ -->
<html>
<head>
<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>"libc++abi" C++ Standard Library Support</title>
<link type="text/css" rel="stylesheet" href="menu.css">
<link type="text/css" rel="stylesheet" href="content.css">
</head>
<body>
<div id="menu">
<div>
<a href="http://llvm.org/">LLVM Home</a>
</div>
<div class="submenu">
<label>libc++abi Info</label>
<a href="/index.html">About</a>
</div>
<div class="submenu">
<label>Quick Links</label>
Update to new lists.llvm.org llvm-svn: 244004
2015-08-05 12:01:26 +08:00
<a href="http://lists.llvm.org/mailman/listinfo/cfe-dev">cfe-dev</a>
<a href="http://lists.llvm.org/mailman/listinfo/cfe-commits">cfe-commits</a>
initial import llvm-svn: 130921
2011-05-05 23:27:28 +08:00
<a href="http://llvm.org/bugs/">Bug Reports</a>
<a href="http://llvm.org/svn/llvm-project/libcxxabi/trunk/">Browse SVN</a>
<a href="http://llvm.org/viewvc/llvm-project/libcxxabi/trunk/">Browse ViewVC</a>
</div>
</div>
<div id="content">
<!--*********************************************************************-->
<h1>"libc++abi" C++ Standard Library Support</h1>
<!--*********************************************************************-->
<p>libc++abi is a new implementation of low level support for a standard
C++ library.</p>
<p>All of the code in libc++abi is <a
href="http://llvm.org/docs/DeveloperPolicy.html#license">dual licensed</a>
under the MIT license and the UIUC License (a BSD-like license).</p>
<!--=====================================================================-->
<h2 id="goals">Features and Goals</h2>
<!--=====================================================================-->
<ul>
<li>Correctness as defined by the C++11 standard.</li>
add a link to the libc++ website llvm-svn: 160553
2012-07-21 01:21:42 +08:00
<li>Provide a portable sublayer to ease the porting of <a href="http://libcxx.llvm.org/">libc++</a></li>
Add goal llvm-svn: 131703
2011-05-20 07:38:38 +08:00
<li>On Mac OS X, be ABI compatible with the existing low-level support.</li>
initial import llvm-svn: 130921
2011-05-05 23:27:28 +08:00
</ul>
<!--=====================================================================-->
<h2 id="requirements">Platform Support</h2>
<!--=====================================================================-->
<p>libc++abi is known to work on the following platforms, using clang.</p>
<ul>
Update status. llvm-svn: 161221
2012-08-03 06:06:41 +08:00
<li>Darwin</li>
initial import llvm-svn: 130921
2011-05-05 23:27:28 +08:00
</ul>
<!--=====================================================================-->
<h2 id="dir-structure">Current Status</h2>
<!--=====================================================================-->
Update status. llvm-svn: 161221
2012-08-03 06:06:41 +08:00
<p>libc++abi is complete. <a href="spec.html">Here</a> is a
list of functionality.</p>
initial import llvm-svn: 130921
2011-05-05 23:27:28 +08:00
<!--=====================================================================-->
<h2>Get it and get involved!</h2>
<!--=====================================================================-->
<p>To check out the code, use:</p>
<ul>
<li><code>svn co http://llvm.org/svn/llvm-project/libcxxabi/trunk libcxxabi</code></li>
</ul>
Add a cmake build system. Will add support for tests with lit in a later patch. This does not yet support building the unwinder in src/Unwind. llvm-svn: 212286
2014-07-04 03:35:48 +08:00
<p>To build:</p>
<ul>
<li>Check out libcxxabi into <code>llvm/projects</code></li>
<li><code>cd llvm</code></li>
<li><code>mkdir build &amp;&amp; cd build</code></li>
<li><code>cmake .. # on linux you may need to prefix with CC=clang CXX=clang++</code></li>
<li><code>make</code></li>
</ul>
<p>To do a standalone build:</p>
<ul>
[libcxxabi] Teach CMake better ways to find the libc++ source directory (and misc cleanup). Summary: The main section of this patch teaches CMake a new option `LIBCXXABI_LIBCXX_PATH` that specifies the path to the libcxx source root. This information is passed to lit so that it can better find libc++'s python module. `LIBCXXABI_LIBCXX_PATH` is also used to help find the libc++ headers. The rest of this patch is misc cleanup, mostly to make pep8 and pylint happy. I've also copied libc++'s .gitignore into libc++abi. Reviewers: jroelofs, danalbert Reviewed By: danalbert Subscribers: cfe-commits Differential Revision: http://reviews.llvm.org/D7130 llvm-svn: 226855
2015-01-23 04:00:06 +08:00
<li>
Check out the <a href="http://libcxx.llvm.org">libcxx source</a> tree.
</li>
Add a cmake build system. Will add support for tests with lit in a later patch. This does not yet support building the unwinder in src/Unwind. llvm-svn: 212286
2014-07-04 03:35:48 +08:00
<li><code>cd libcxxabi</code></li>
<li><code>mkdir build &amp;&amp; cd build</code></li>
[libcxxabi] Teach CMake better ways to find the libc++ source directory (and misc cleanup). Summary: The main section of this patch teaches CMake a new option `LIBCXXABI_LIBCXX_PATH` that specifies the path to the libcxx source root. This information is passed to lit so that it can better find libc++'s python module. `LIBCXXABI_LIBCXX_PATH` is also used to help find the libc++ headers. The rest of this patch is misc cleanup, mostly to make pep8 and pylint happy. I've also copied libc++'s .gitignore into libc++abi. Reviewers: jroelofs, danalbert Reviewed By: danalbert Subscribers: cfe-commits Differential Revision: http://reviews.llvm.org/D7130 llvm-svn: 226855
2015-01-23 04:00:06 +08:00
<li><code>cmake -DLIBCXXABI_LIBCXX_PATH=path/to/libcxx .. # on
Add lit configs for libcxxabi tests. This makes running libcxxabi tests on Linux _much_ easier. Adds a check-libcxxabi target to cmake. Also defaults to building a dynamic libc++abi. This is so that the default options still test the libc++abi that is being built. There are two problems with testing a static libc++abi. In the case of a standalone build, the tests will link the system's libc++, which might not have been built against our libc++abi. In the case of an in tree build, libc++ will prefer a dynamic libc++abi from the system over a static libc++abi from the output directory. llvm-svn: 212672
2014-07-10 10:20:11 +08:00
linux you may need -DCMAKE_C_COMPILER=clang -DCMAKE_CXX_COMPILER=clang++</code></li>
Add a cmake build system. Will add support for tests with lit in a later patch. This does not yet support building the unwinder in src/Unwind. llvm-svn: 212286
2014-07-04 03:35:48 +08:00
<li><code>make</code></li>
</ul>
[libcxxabi] Document the standalone build's requirements on llvm-config and llvm sources. The current documentation does not explain that the standalone build requires the LLVM sources. This patch updates the documentation to reflect this requirement and explains how to manually specify the location of the required files. llvm-svn: 220049
2014-10-18 00:32:06 +08:00
<p> By default CMake uses <code>llvm-config</code> to locate the required
LLVM sources. If CMake cannot find <code>llvm-config</code> then you must
configure CMake using either of the following options.
</p>
<ul>
[CMake] Apply r279151 cleanup to libc++abi. This patch applies changes similar to those in r279515 to libc++abi. Summary of changes in this patch: * Renamed variable LLVM_CONFIG -> LLVM_CONFIG_PATH * Renamed variable LIBCXXABI_BUILT_STANDALONE -> LIBCXXABI_STANDALONE_BUILD * Add an include of AddLLVM in the tests subdirectory for add_lit_testsuite. llvm-svn: 279936
2016-08-29 02:16:18 +08:00
<li><code>-DLLVM_CONFIG_PATH=path/to/llvm-config</code></li>
[libcxxabi] Document the standalone build's requirements on llvm-config and llvm sources. The current documentation does not explain that the standalone build requires the LLVM sources. This patch updates the documentation to reflect this requirement and explains how to manually specify the location of the required files. llvm-svn: 220049
2014-10-18 00:32:06 +08:00
<li><code>-DLLVM_PATH=path/to/llvm-source-root</code></li>
</ul>
</p>
Add a cmake build system. Will add support for tests with lit in a later patch. This does not yet support building the unwinder in src/Unwind. llvm-svn: 212286
2014-07-04 03:35:48 +08:00
Add lit configs for libcxxabi tests. This makes running libcxxabi tests on Linux _much_ easier. Adds a check-libcxxabi target to cmake. Also defaults to building a dynamic libc++abi. This is so that the default options still test the libc++abi that is being built. There are two problems with testing a static libc++abi. In the case of a standalone build, the tests will link the system's libc++, which might not have been built against our libc++abi. In the case of an in tree build, libc++ will prefer a dynamic libc++abi from the system over a static libc++abi from the output directory. llvm-svn: 212672
2014-07-10 10:20:11 +08:00
<p>To run the tests:</p>
<ul>
[CMake] Be more consistent about naming targets and components in libc++abi This patch (and commit summary) mirror r279675 by Chris B which was applied to libc++ but not libc++abi. Summary: The point of this patch is to have a consistent convention for naming build, check and install targets so that the targets can be constructed from the project name. This change renames a bunch of CMake components and targets from libcxxabi to cxxabi. For each renamed target I've added a convenience target that matches the old target name and depends on the new target. This will preserve function of the old targets so that the change doesn't break the world. We can evaluate if it is worth removing the extra targets later. llvm-svn: 279938
2016-08-29 02:28:51 +08:00
<li><code>make check-cxxabi</code></li>
Add lit configs for libcxxabi tests. This makes running libcxxabi tests on Linux _much_ easier. Adds a check-libcxxabi target to cmake. Also defaults to building a dynamic libc++abi. This is so that the default options still test the libc++abi that is being built. There are two problems with testing a static libc++abi. In the case of a standalone build, the tests will link the system's libc++, which might not have been built against our libc++abi. In the case of an in tree build, libc++ will prefer a dynamic libc++abi from the system over a static libc++abi from the output directory. llvm-svn: 212672
2014-07-10 10:20:11 +08:00
</ul>
<p>Note: in a standalone build, the system's libc++ will be used for tests. If
the system's libc++ was statically linked against libc++abi (or linked against
a different ABI library), this may interfere with test results.</p>
initial import llvm-svn: 130921
2011-05-05 23:27:28 +08:00
<p>Send discussions to the
Update to new lists.llvm.org llvm-svn: 244004
2015-08-05 12:01:26 +08:00
(<a href="http://lists.llvm.org/mailman/listinfo/cfe-dev">clang mailing list</a>).</p>
initial import llvm-svn: 130921
2011-05-05 23:27:28 +08:00
Add a FAQ section, with a question about why the std::exception class destructors live in libc++abi llvm-svn: 210661
2014-06-12 00:54:09 +08:00
<!--=====================================================================-->
<h2>Frequently asked questions</h2>
<!--=====================================================================-->
<p>Q: Why are the destructors for the standard exception classes defined in libc++abi?
They're just empty, can't they be defined inline?</p>
<p>A: The destructors for them live in libc++abi because they are "key" functions.
The Itanium ABI describes a "key" function as the first virtual declared.
And wherever the key function is defined, that is where the <code>type_info</code> gets defined.
And in libc++ types are the same type if and only if they have the same <code>type_info</code>
(as in there must be only one type info per type in the entire application).
And on OS X, libstdc++ and libc++ share these exception types.
So to be able to throw in one dylib and catch in another (a <code>std::exception</code> for example),
there must be only one <code>std::exception type_info</code> in the entire app.
That typeinfo gets laid down beside <code>~exception()</code> in libc++abi (for both libstdc++ and libc++).</p>
<p>--Howard Hinnant</p>
initial import llvm-svn: 130921
2011-05-05 23:27:28 +08:00
</div>
</body>
</html>