1
0
mirror of https://github.com/RPCS3/llvm-mirror.git synced 2024-11-23 11:13:28 +01:00
llvm-mirror/lib/Support/Unix
Zachary Turner 3d2387c8ac Attempt 3: Resubmit "[Support] Expose flattenWindowsCommandLine."
I took some liberties and quoted fewer characters than before,
based on an article from MSDN which says that only certain characters
cause an arg to require quoting.  This seems to be incorrect, though,
and worse it seems to be a difference in Windows version.  The bot
that fails is Windows 7, and I can't reproduce the failure on Win
10.  But it's definitely related to quoting and special characters,
because both tests that fail have a * in the argument, which is one
of the special characters that would cause an argument to be quoted
before but not any longer after the new patch.

Since I don't have Win 7, all I can do is just guess that I need to
restore the old quoting rules.  So this patch does that in hopes that
it fixes the problem on Windows 7.

llvm-svn: 334375
2018-06-10 20:57:14 +00:00
..
COM.inc
DynamicLibrary.inc
Host.inc [Support] Avoid normalization in sys::getDefaultTargetTriple 2018-05-25 20:39:37 +00:00
Memory.inc [Support] Use zx_cache_flush on Fuchsia to flush instruction cache 2018-06-06 06:26:18 +00:00
Mutex.inc
Path.inc Cleanup. NFC 2018-06-10 04:53:14 +00:00
Process.inc Cleanup. NFC 2018-06-10 04:53:14 +00:00
Program.inc Attempt 3: Resubmit "[Support] Expose flattenWindowsCommandLine." 2018-06-10 20:57:14 +00:00
README.txt
RWMutex.inc
Signals.inc Signal handling should be signal-safe 2018-05-16 17:25:35 +00:00
Threading.inc Remove a dead #ifdef. 2018-04-30 00:08:06 +00:00
ThreadLocal.inc IWYU for llvm-config.h in llvm, additions. 2018-04-30 14:59:11 +00:00
Unix.h Remove @brief commands from doxygen comments, too. 2018-05-01 16:10:38 +00:00
Watchdog.inc IWYU for llvm-config.h in llvm, additions. 2018-04-30 14:59:11 +00:00

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.