RPCS3/llvm-mirror
1
0
Fork 0
mirror of https://github.com/RPCS3/llvm-mirror.git synced 2024-11-25 20:23:11 +01:00
Code Issues Projects Releases Wiki Activity
428972ecad
llvm-mirror/lib/System/Unix
History
Chris Lattner faf39c40d4 Add a new 'AddSignalHandler' function to Signals.h that allows 
arbitrary functions to be run when a crash happens.  Delete 
RemoveDirectoryOnSignal as it is dead and has never had clients.

Change PrintStackTraceOnErrorSignal to be implemented in terms of
AddSignalHandler.

I updated the Win32 versions of these APIs, but can't test them.
If there are any problems, I'd be happy to fix them as well.

llvm-svn: 66072
2009-03-04 21:21:36 +00:00
..
Alarm.inc Add a Sleep() function. 2009-02-08 22:47:39 +00:00
Host.inc Add Emacs hints to Alarm.inc. 2009-02-08 21:10:57 +00:00
Memory.inc Update the stub and callback code to handle lazy compilation. The stub 2008-10-20 21:39:23 +00:00
Mutex.inc
Path.inc Fix main executable path name resolution on FreeBSD, patch by 2009-03-02 22:17:15 +00:00
Process.inc Restore code to disable crash catcher on older OS X systems 2008-04-12 00:47:46 +00:00
Program.inc Fix redirection of stderr in sys::Program::ExecuteAndWait. There was logic 2008-06-12 12:53:35 +00:00
README.txt
Signals.inc Add a new 'AddSignalHandler' function to Signals.h that allows 2009-03-04 21:21:36 +00:00
TimeValue.inc
Unix.h Clean up the use of static and anonymous namespaces. This turned up 2008-05-13 00:00:25 +00:00

README.txt 

llvm/lib/System/Unix README
===========================

This directory provides implementations of the lib/System classes that
are common to two or more variants of UNIX. For example, the directory 
structure underneath this directory could look like this:

Unix           - only code that is truly generic to all UNIX platforms
  Posix        - code that is specific to Posix variants of UNIX
  SUS          - code that is specific to the Single Unix Specification 
  SysV         - code that is specific to System V variants of UNIX

As a rule, only those directories actually needing to be created should be
created. Also, further subdirectories could be created to reflect versions of
the various standards. For example, under SUS there could be v1, v2, and v3
subdirectories to reflect the three major versions of SUS.