Lines Matching refs: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
13 facilities are needed and the System Library is the wrapper around those system
16 By centralizing LLVM's use of operating system interfaces, we make it possible
23 Note that the System Library is not intended to be a complete operating system
39 variations in operating system interfaces and doing so efficiently.  The
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
60 The System Library must shield LLVM from **all** system headers. To obtain
61 system level functionality, LLVM source must ``#include "llvm/System/Thing.h"``
62 and nothing else. This means that ``Thing.h`` cannot expose any system header
63 files. This protects LLVM from accidentally using system specific functionality
88 simply wrap each operating system call. It would be preferable to wrap several
89 operating system calls that are always used in conjunction with one another by
94 operating system calls: ``getenv``, ``fork``, ``execve``, and ``wait``. The
97 we don't want is wrappers for the operating system calls involved.
99 There must **not** be a one-to-one relationship between operating system
108 system wrapper here, just enough to satisfy LLVM's needs. And, LLVM doesn't
119 systems supported for a given class of operating system (e.g. Unix, Win32).
132 Any functions defined by system libraries (i.e. not defined by ``lib/System``)
134 file for that function is not exposed. This prevents inadvertent use of system
137 For example, the ``stat`` system call is notorious for having variations in the
148 Any data defined by system libraries (i.e. not defined by ``lib/System``) must
156 Operating system interfaces will generally provide error results for every
161 disk sector", or "system call interrupted". We'll call the first group "*soft*"
202 them to be as efficient as possible.  However, no routines in the system
209 class of operating system. Currently only Unix and Win32 classes are defined
210 but more could be added for other operating system classifications.  To
214 after implementing the generic (operating system independent) functionality
231 operating system that will provide the implementation. The specific details for
240 forward on all operating system. System V IPC on the other hand isn't even
245 for a given operating system.  In all cases, the interface and the