6502/llvm-6502
1
0
Fork 0
mirror of https://github.com/c64scene-ar/llvm-6502.git synced 2024-08-24 09:29:42 +00:00
Code Issues Projects Releases Wiki Activity
29640bcb7d
llvm-6502/lib/Support/Unix
History
Daniel Sanders d3aaad2d26 Revert: r211588 - [mips] Use __clear_cache builtin instead of cacheflush() in Unix Memory::InvalidateInstructionCache() 
Buildbot reports a test failure on the llvm-mips-linux builder and blames r211588.
Although it doesn't appear in the blamelist, it seems it could also be r211587
(because it's committed to compiler-rt?) since they were tested together.

Reverting the most likely suspect (r211588) to confirm one way or the other.


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@211594 91177308-0d34-0410-b5e6-96231b3b80d8
2014-06-24 13:53:56 +00:00
..
Host.inc Support: normalize the default triple on Unix 2014-03-30 03:22:37 +00:00
Memory.inc Revert: r211588 - [mips] Use __clear_cache builtin instead of cacheflush() in Unix Memory::InvalidateInstructionCache() 2014-06-24 13:53:56 +00:00
Mutex.inc
Path.inc Finishing touch for the std::error_code transition. 2014-06-13 17:20:48 +00:00
Process.inc Remove 'using std::errro_code' from lib. 2014-06-13 02:24:39 +00:00
Program.inc Remove 'using std::errro_code' from lib. 2014-06-13 02:24:39 +00:00
README.txt
RWMutex.inc Fix RWMutex to be thread-safe when pthread_rwlock is not available 2014-03-01 04:30:32 +00:00
Signals.inc [C++] Use 'nullptr'. 2014-04-28 04:05:08 +00:00
ThreadLocal.inc Make sys::ThreadLocal<> zero-initialized on non-thread builds (PR18205) 2013-12-19 20:32:44 +00:00
TimeValue.inc [C++] Use 'nullptr'. 2014-04-28 04:05:08 +00:00
Unix.h Fix build on Solaris 11. 2013-10-08 16:12:58 +00:00
Watchdog.inc Add a new watchdog timer interface. The interface does not permit handling timeouts, so 2013-03-26 01:27:52 +00:00

README.txt 

llvm/lib/Support/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.