llvm-6502

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

History

Michael J. Spencer 44edb0bd0c Don't cast Win32 FILETIME structs to int64. Patch by Dimitry Andric! According to the Microsoft documentation here: http://msdn.microsoft.com/en-us/library/ms724284%28VS.85%29.aspx this cast used in lib/System/Win32/Path.inc: __int64 ft = reinterpret_cast<__int64>(&fi.ftLastWriteTime); should not be done. The documentation says: "Do not cast a pointer to a FILETIME structure to either a ULARGE_INTEGER* or __int64* value because it can cause alignment faults on 64-bit Windows." git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@112376 91177308-0d34-0410-b5e6-96231b3b80d8		2010-08-28 16:39:32 +00:00
..
Unix	CrashRecovery/Darwin: On Darwin, raise sends a signal to the main thread instead	2010-08-19 23:45:39 +00:00
Win32	Don't cast Win32 FILETIME structs to int64. Patch by Dimitry Andric!	2010-08-28 16:39:32 +00:00
Alarm.cpp
Atomic.cpp	Fixes the Atomic implementation if compiled by MSVC compiler.	2009-12-07 05:29:59 +00:00
CMakeLists.txt	Tell Valgrind when we modify already-executed machine code so it knows	2010-03-15 04:57:55 +00:00
Disassembler.cpp	Avoid "variable 'bits' set but not used [-Wunused-but-set-variable]"	2010-06-10 16:23:15 +00:00
DynamicLibrary.cpp	Fix failure of unittests/ExecutionEngine/JIT/MultiJITTest.cpp on	2010-08-17 15:42:43 +00:00
Errno.cpp
Host.cpp	Stubs for getHostCPUFeatures API. This implements part of PR5389.	2010-01-19 21:26:05 +00:00
IncludeFile.cpp
Makefile	mark some libraries that currently require RTTI.	2010-01-24 20:22:08 +00:00
Memory.cpp	Tell Valgrind when we modify already-executed machine code so it knows	2010-03-15 04:57:55 +00:00
Mutex.cpp
Path.cpp	Don't bother checking canRead() before calling getMagicNumber();	2010-05-27 17:12:23 +00:00
Process.cpp
Program.cpp	unnest from namespace.	2010-04-18 03:33:55 +00:00
README.txt
RWMutex.cpp	Mark this variable as used.	2010-08-10 10:39:25 +00:00
SearchForAddressOfSpecialSymbol.cpp	Make clang bootstrap happier on OSX 10.5 by reducing the number of headers	2010-03-11 06:14:32 +00:00
Signals.cpp
Threading.cpp
ThreadLocal.cpp	Fix --disable-threads build, PR7949.	2010-08-20 20:54:37 +00:00
TimeValue.cpp
Valgrind.cpp	Tell Valgrind when we modify already-executed machine code so it knows	2010-03-15 04:57:55 +00:00

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