Lines Matching full:operating

10 to shield LLVM from the differences between operating systems for the few
11 services LLVM needs from the operating system. Much of LLVM is written using
16 By centralizing LLVM's use of operating system interfaces, we make it possible
20 specific operating systems. Such uses are replaced with simple calls to the
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
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
107 that isn't actually used by LLVM. We're not writing a general purpose operating
117 implementation to multiple operating systems if those operating systems can
118 share the same implementation. This rule applies to the set of operating
119 systems supported for a given class of operating system (e.g. Unix, Win32).
156 Operating system interfaces will generally provide error results for every
173 function. For many operating systems, if the file doesn't exist, attempting to
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