llvm-6502/lib/System
Owen Anderson 02b97355aa Fix compilation without pthreads.
Patch by Xerxes Ranby.


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@74283 91177308-0d34-0410-b5e6-96231b3b80d8
2009-06-26 08:48:03 +00:00
..
Unix Fix compilation without pthreads. 2009-06-26 08:48:03 +00:00
Win32 Fix error in the Win32 implementation pointed out by Howard Su. 2009-06-26 00:51:20 +00:00
Alarm.cpp Remove uses of llvm/System/IncludeFile.h that are no longer needed. 2008-05-06 01:32:53 +00:00
Atomic.cpp Add atomic multiply and divide operations, built on top of CompareAndSwap. 2009-06-23 21:19:04 +00:00
CMakeLists.txt Update cmake build files. 2009-06-25 21:58:34 +00:00
Disassembler.cpp hasDisassembler should return false if disassembler isn't available. 2008-11-04 06:09:38 +00:00
DynamicLibrary.cpp Guard dynamic library loading. 2009-06-25 18:12:44 +00:00
Host.cpp Add llvm::sys::{osName,osVersion} for retrieving operating system name 2008-10-02 01:17:28 +00:00
IncludeFile.cpp Specialize FORCE_DEFINING_FILE_TO_BE_LINKED using a GCC trick 2008-03-21 23:38:23 +00:00
LICENSE.TXT License for this library. 2004-08-25 00:48:02 +00:00
Makefile Removed trailing whitespace from Makefiles. 2009-01-09 16:44:42 +00:00
Memory.cpp ARM / Mac OS X also wants to invalidate icache after jitting. 2008-11-14 02:33:17 +00:00
Mutex.cpp Insert a SmartMutex templated class into the class hierarchy, which takes a template parameter specifying whether this mutex 2009-06-18 17:53:17 +00:00
Path.cpp Fix g++-4.4.0 warning, it was causing llvm-nm to fail on wrapped BC files: 2009-04-25 10:25:12 +00:00
Process.cpp Remove uses of llvm/System/IncludeFile.h that are no longer needed. 2008-05-06 01:32:53 +00:00
Program.cpp Remove uses of llvm/System/IncludeFile.h that are no longer needed. 2008-05-06 01:32:53 +00:00
README.txt For PR797: 2006-08-25 19:54:53 +00:00
RWMutex.cpp Workaround for an... interesting bug in Darwin's pthread_rwlock_init. 2009-06-20 00:32:27 +00:00
Signals.cpp Remove uses of llvm/System/IncludeFile.h that are no longer needed. 2008-05-06 01:32:53 +00:00
Threading.cpp Move Threading.[h|cpp] from Support to System. 2009-06-18 16:54:52 +00:00
ThreadLocal.cpp Fix unused variable warnings. 2009-06-26 01:34:35 +00:00
TimeValue.cpp Remove attribution from file headers, per discussion on llvmdev. 2007-12-29 20:36:04 +00:00

Design Of lib/System
====================

The software in this directory is designed to completely shield LLVM from any
and all operating system specific functionality. It is not intended to be a
complete operating system wrapper (such as ACE), but only to provide the
functionality necessary to support LLVM.

The software located here, of necessity, has very specific and stringent design
rules. Violation of these rules means that cracks in the shield could form and
the primary goal of the library is defeated. By consistently using this library,
LLVM becomes more easily ported to new platforms since the only thing requiring 
porting is this library.

Complete documentation for the library can be found in the file:
  llvm/docs/SystemLibrary.html 
or at this URL:
  http://llvm.org/docs/SystemLibrary.html

While we recommend that you read the more detailed documentation, for the 
impatient, here's a high level summary of the library's requirements.

 1. No system header files are to be exposed through the interface.
 2. Std C++ and Std C header files are okay to be exposed through the interface.
 3. No exposed system-specific functions.
 4. No exposed system-specific data.
 5. Data in lib/System classes must use only simple C++ intrinsic types.
 6. Errors are handled by returning "true" and setting an optional std::string
 7. Library must not throw any exceptions, period.
 8. Interface functions must not have throw() specifications.
 9. No duplicate function impementations are permitted within an operating
    system class.

To accomplish these requirements, the library has numerous design criteria that 
must be satisfied. Here's a high level summary of the library's design criteria:

 1. No unused functionality (only what LLVM needs)
 2. High-Level Interfaces
 3. Use Opaque Classes
 4. Common Implementations</a></li>
 5. Multiple Implementations</a></li>
 6. Minimize Memory Allocation</a></li>
 7. No Virtual Methods