diff options
author | Edward O'Callaghan <eocallaghan@auroraux.org> | 2009-08-03 01:26:42 +0000 |
---|---|---|
committer | Edward O'Callaghan <eocallaghan@auroraux.org> | 2009-08-03 01:26:42 +0000 |
commit | f998156715cdf8ba5d07ab8c853d803a22867e77 (patch) | |
tree | 6dc96f88db248f22692699983df48c49aaaec864 | |
parent | d904635616ca27a56531375a7d25547c930a4040 (diff) |
Small improvement to Compiler-RT docs and add a CREDITS.TXT file to source.
git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@77934 91177308-0d34-0410-b5e6-96231b3b80d8
-rw-r--r-- | CREDITS.TXT | 16 | ||||
-rw-r--r-- | www/index.html | 24 |
2 files changed, 39 insertions, 1 deletions
diff --git a/CREDITS.TXT b/CREDITS.TXT new file mode 100644 index 000000000..c73c760d3 --- /dev/null +++ b/CREDITS.TXT @@ -0,0 +1,16 @@ +This file is a partial list of people who have contributed to the LLVM/CompilerRT +project. If you have contributed a patch or made some other contribution to +LLVM/CompilerRT, please submit a patch to this file to add yourself, and it will be +done! + +The list is sorted by surname and formatted to allow easy grepping and +beautification by scripts. The fields are: name (N), email (E), web-address +(W), PGP key ID and fingerprint (P), description (D), and snail-mail address +(S). + +N: Edward O'Callaghan +E: eocallaghan@auroraux.org +W: http://www.auroraux.org +D: CMake'ify Compiler-RT build system +D: Maintain Solaris & AuroraUX ports of Compiler-RT + diff --git a/www/index.html b/www/index.html index c4306cd2f..fc40b7e4c 100644 --- a/www/index.html +++ b/www/index.html @@ -61,7 +61,29 @@ <li>A target-independent implementation of the Apple "Blocks" runtime interfaces.</li> </ul> - + + <!--=====================================================================--> + <h2 id="dir-structure">Source Structure</h2> + <!--=====================================================================--> + + <p>A short explanation of the directory structure of compiler-rt:</p> + + <p>For testing it is possible to build a generic library and an optimized library. + The optimized library is formed by overlaying the optimized versions onto the generic library. + Of course, some architectures have additional functions, + so the optimized library may have functions not found in the generic version.</p> + + <ul> + <li> lib/ Is a generic portable implementations.</li> + <li> lib/<arch> has optimized version for the following supported architectures: + <ul> + <li>i386</li> + <li>X86-64</li> + <li>PowerPC</li> + <li>PowerPC 64</li> + </ul></li> + </ul> + <!--=====================================================================--> <h2>Get it and get involved!</h2> <!--=====================================================================--> |