llvm-6502

mirror of https://github.com/c64scene-ar/llvm-6502.git synced 2024-11-08 04:07:07 +00:00

History

Dan Gohman dd17b25611 Don't use plain %x to print pointer values. I had changed it from %p since %p isn't formatted consistently, but obviously plain %x is wrong. PRIxPTR with a cast to uintptr_t would work here, but that requires inconvenient build-system changes. %lu works on all current and foreseable future hosts. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@60616 91177308-0d34-0410-b5e6-96231b3b80d8		2008-12-05 23:39:24 +00:00
..
Unix	Don't use plain %x to print pointer values. I had changed it from %p	2008-12-05 23:39:24 +00:00
Win32
Alarm.cpp
CMakeLists.txt	CMake: when bulding shared libraries on non-WIN32 systems, link dl to	2008-11-12 20:40:56 +00:00
Disassembler.cpp	hasDisassembler should return false if disassembler isn't available.	2008-11-04 06:09:38 +00:00
DynamicLibrary.cpp
Host.cpp
IncludeFile.cpp
LICENSE.TXT
Makefile
Memory.cpp	ARM / Mac OS X also wants to invalidate icache after jitting.	2008-11-14 02:33:17 +00:00
Mutex.cpp	plug leakage of mutex data. pthread_mutex_destroy() doesnt free our malloc'ed memory.	2008-11-06 16:21:49 +00:00
Path.cpp
Process.cpp
Program.cpp
README.txt
Signals.cpp
TimeValue.cpp

README.txt

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