Lines Matching full:system

11 services LLVM needs from the operating system. Much of LLVM is written using
12 portability features of standard C++. However, in a few areas, system dependent
14 system calls.
16 By centralizing LLVM's use of operating system interfaces, we make it possible
23 Note that the Support Library is not intended to be a complete operating system
28 The Support Library was originally referred to as the System Library, written
30 from the eXtensible Programming System (XPS). Several people helped with the
39 variations in operating system interfaces and doing so efficiently.  The
42 Don't Include System Headers
46 system header. Care has been taken to remove all such ``#includes`` from LLVM
52 To obtain system-dependent functionality, existing interfaces to the system
57 Don't Expose System Headers
60 The Support Library must shield LLVM from **all** system headers. To obtain
61 system level functionality, LLVM source must
63 ``Thing.h`` cannot expose any system header files. This protects LLVM from
64 accidentally using system specific functionality and only allows it via
89 simply wrap each operating system call. It would be preferable to wrap several
90 operating system calls that are always used in conjunction with one another by
95 operating system calls: ``getenv``, ``fork``, ``execve``, and ``wait``. The
98 we don't want is wrappers for the operating system calls involved.
100 There must **not** be a one-to-one relationship between operating system
109 system wrapper here, just enough to satisfy LLVM's needs. And, LLVM doesn't
120 systems supported for a given class of operating system (e.g. Unix, Win32).
133 Any functions defined by system libraries (i.e. not defined by ``lib/Support``)
135 file for that function is not exposed. This prevents inadvertent use of system
138 For example, the ``stat`` system call is notorious for having variations in the
149 Any data defined by system libraries (i.e. not defined by ``lib/Support``) must
157 Operating system interfaces will generally provide error results for every
162 disk sector", or "system call interrupted". We'll call the first group "*soft*"
203 need them to be as efficient as possible.  However, no routines in the system
210 class of operating system. Currently only Unix and Win32 classes are defined
211 but more could be added for other operating system classifications.  To
214 ``lib/Support``, after implementing the generic (operating system independent)
231 of operating system that will provide the implementation. The specific details
240 forward on all operating system. System V IPC on the other hand isn't even
241 supported on all platforms. Instead of "supporting" System V IPC,
243 inter-process communications. The implementations might use System V IPC if
245 for a given operating system.  In all cases, the interface and the