1. [libFuzzer] Fix minimizing timeouts (details)
  2. [AARCH64] [MC] add memtag as an alias of mte architecture extension (details)
  3. [libc][obvious] Remove a commented out block. (details)
  4. [LLDB] Improve PDB discovery (details)
Commit 9df7ee34e1b557908c125e9036ad8c54da71a4ef by iii
[libFuzzer] Fix minimizing timeouts

When one tries to minimize timeouts using -minimize_crash=1,
minimization immediately fails. The following sequence of events is
responsible for this:

[parent] SIGALRM occurs
[parent] read() returns -EINTR (or -ERESTARTSYS according to strace)
[parent] fgets() returns NULL
[parent] ExecuteCommand() closes child's stdout and returns
[child ] SIGALRM occurs
[child ] AlarmCallback() attempts to write "ALARM: ..." to stdout
[child ] Dies with SIGPIPE without calling DumpCurrentUnit()
[parent] Does not see -exact_artifact_path and exits

When minimizing, the timer in parent is not necessary, so fix by not
setting it in this case.

Reviewed By: morehouse

Differential Revision:
The file was modifiedcompiler-rt/lib/fuzzer/FuzzerUtilFuchsia.cpp
The file was modifiedcompiler-rt/lib/fuzzer/FuzzerUtilWindows.cpp
The file was modifiedcompiler-rt/lib/fuzzer/FuzzerOptions.h
The file was modifiedcompiler-rt/lib/fuzzer/FuzzerDriver.cpp
The file was addedcompiler-rt/test/fuzzer/minimize_timeout.test
The file was modifiedcompiler-rt/lib/fuzzer/FuzzerUtilPosix.cpp
Commit 277873ce0f484e8cb5cb99dade63c7a93d99bd3b by caij2003
[AARCH64] [MC] add memtag as an alias of mte architecture extension

Add memtag as an alis of met architectture extesion to be consistent
with GNU as.


Reviewed By: nickdesaulniers, MaskRay

Differential Revision:
The file was modifiedllvm/lib/Target/AArch64/AsmParser/AArch64AsmParser.cpp
The file was modifiedllvm/test/MC/AArch64/directive-arch_extension.s
Commit df79e18796d09f33d15974c55cca8b2b5b484e1f by sivachandra
[libc][obvious] Remove a commented out block.
The file was modifiedlibc/utils/UnitTest/Test.cpp
Commit 479f5bfdb02b191f03b3de1a7c3d5a5098b3fcaf by amccarth
[LLDB] Improve PDB discovery

When loading a PE/COFF target, the associated PDB file often wasn't
found.  The executable module contains a path for the associated PDB
file, but people often debug from a different directory than the one
their build system uses.  (This is especially common in post-mortem
and cross platform debugging.)

Suppose the COFF executable being debugged is `~/proj/foo.exe`, but
it was built elsewhere and refers to `D:\remote\build\env\foobar.pdb`,
LLDB wouldn't find it.

With this change, if no file exists at the PDB path, LLDB will look
in the executable directory for a PDB file that matches the name of
the one it expected (e.g., `~/proj/foobar.pdb`).  If found, the PDB
is subject to the same matching criteria (GUIDs and age) as would
have been used had it been in the original location.

This same-directory-as-the-binary rule is commonly used by debuggers
on Windows.

Differential Review:
The file was addedlldb/test/Shell/SymbolFile/NativePDB/locate-pdb.cpp
The file was modifiedlldb/source/Plugins/SymbolFile/NativePDB/SymbolFileNativePDB.cpp
The file was addedlldb/test/Shell/SymbolFile/NativePDB/Inputs/locate-pdb.lldbinit