llvm-6502/lib/Support
2013-07-10 17:30:39 +00:00
..
Unix Use status to implement file_size. 2013-07-10 17:16:40 +00:00
Windows Use status to implement file_size. 2013-07-10 17:16:40 +00:00
Allocator.cpp
APFloat.cpp [APFloat] Swap an early out check so we do not dereference str.end(). 2013-07-02 15:50:05 +00:00
APInt.cpp
APSInt.cpp
Atomic.cpp
BlockFrequency.cpp Fix a bad overflow check pointed out by Ben. 2013-06-28 21:51:18 +00:00
BranchProbability.cpp
circular_raw_ostream.cpp
CMakeLists.txt Rename PathV2 to just Path now that it is the only one. 2013-06-26 19:33:03 +00:00
CommandLine.cpp
Compression.cpp
ConstantRange.cpp
ConvertUTF.c
ConvertUTFWrapper.cpp
COPYRIGHT.regex
CrashRecoveryContext.cpp
DAGDeltaAlgorithm.cpp
DataExtractor.cpp
DataStream.cpp
Debug.cpp
DeltaAlgorithm.cpp
Disassembler.cpp
Dwarf.cpp
DynamicLibrary.cpp
Errno.cpp
ErrorHandling.cpp
FileOutputBuffer.cpp Create files with the correct permission instead of changing it afterwards. 2013-07-08 15:22:09 +00:00
FileUtilities.cpp MemoryBuffer::getFile handles zero sized files, no need to duplicate the test. 2013-07-10 17:30:39 +00:00
FoldingSet.cpp
FormattedStream.cpp
GraphWriter.cpp Find xdot or xdot.py. 2013-07-08 20:24:54 +00:00
Hashing.cpp
Host.cpp
IncludeFile.cpp
IntEqClasses.cpp
IntervalMap.cpp
IntrusiveRefCntPtr.cpp
IsInf.cpp
IsNAN.cpp
LLVMBuild.txt
Locale.cpp
LocaleGeneric.inc
LocaleWindows.inc
LocaleXlocale.inc
LockFileManager.cpp Add a createUniqueFile function and switch llvm's users of unique_file. 2013-07-05 21:01:08 +00:00
Makefile
ManagedStatic.cpp
MD5.cpp
Memory.cpp
MemoryBuffer.cpp keep only the StringRef version of getFileOrSTDIN. 2013-06-25 05:28:34 +00:00
MemoryObject.cpp
Mutex.cpp
Path.cpp Remove unique_file now that it is unused. 2013-07-05 21:19:35 +00:00
PluginLoader.cpp
PrettyStackTrace.cpp
Process.cpp
Program.cpp
raw_os_ostream.cpp
raw_ostream.cpp
README.txt.system
regcclass.h
regcname.h
regcomp.c
regengine.inc
regerror.c
regex2.h
regex_impl.h
Regex.cpp
regexec.c
regfree.c
regstrlcpy.c
regutils.h
RWMutex.cpp
SearchForAddressOfSpecialSymbol.cpp
Signals.cpp
SmallPtrSet.cpp
SmallVector.cpp
SourceMgr.cpp
Statistic.cpp
StreamableMemoryObject.cpp
StringExtras.cpp
StringMap.cpp
StringPool.cpp
StringRef.cpp Revert r185852. 2013-07-08 20:27:34 +00:00
StringRefMemoryObject.cpp
system_error.cpp
SystemUtils.cpp
TargetRegistry.cpp
Threading.cpp
ThreadLocal.cpp
Timer.cpp
TimeValue.cpp
ToolOutputFile.cpp
Triple.cpp
Twine.cpp
Valgrind.cpp
Watchdog.cpp
YAMLParser.cpp
YAMLTraits.cpp Use SmallVectorImpl::iterator/const_iterator instead of SmallVector to avoid specifying the vector size. 2013-07-04 01:31:24 +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
 5. Multiple Implementations
 6. Minimize Memory Allocation
 7. No Virtual Methods