Changes

[X86] Try to avoid casts around logical vector ops recursively.
Currently PromoteMaskArithemtic only looks at a single operation to skip
casts. This means we miss cases where we combine multiple masks.
This patch updates PromoteMaskArithemtic to try to recursively promote 
AND/XOR/AND nodes that terminate in truncates of the right size or 
constant vectors.
Reviewers: craig.topper, RKSimon, spatel
Reviewed By: RKSimon
Differential Revision: https://reviews.llvm.org/D72524

Reorder targets in alphabetical order. NFC.

PR42108 Consistently diagnose binding a reference template parameter to
a temporary.
We previously failed to materialize a temporary when performing an 
implicit conversion to a reference type, resulting in our thinking the 
argument was a value rather than a reference in some cases.

List implicit operator== after implicit destructors in a vtable.
Summary: We previously listed first declared members, then implicit
operator=, then implicit operator==, then implicit destructors. Per
discussion on https://github.com/itanium-cxx-abi/cxx-abi/issues/88, put
the implicit equality comparison operators at the very end, after all
special member functions.
Reviewers: rjmccall
Subscribers: cfe-commits
Tags: #clang
Differential Revision: https://reviews.llvm.org/D72897

Undo changes to release notes intended for the Clang 10 branch, not
master.

[libc++][libc++abi] Fix or suppress failing tests in single-threaded
builds.
Fix a libc++abi test that was incorrectly checking for threading 
primitives even when threading was disabled.
Additionally, temporarily XFAIL some module tests that fail because the
<atomic> header is unsupported but still built as a part of the std
module.
To properly address this libc++ would either need to produce a different 
module.modulemap for single-threaded configurations, or it would need to
make the <atomic> header not hard-error and instead be empty for
single-threaded configurations

[mlir] NFC: Fix trivial typos in comments
Differential Revision: https://reviews.llvm.org/D73012

[StackColoring] Remap FixedStackPseudoSourceValue frame index referenced
by MachineMemOperand
StackColoring::remapInstructions() remaps MachineOperand frame index
(e.g. %stack.1 -> %stack.0) but does not remap
FixedStackPseudoSourceValue frame index (e.g. store 4 into
%stack.1.ap2.i.i) referenced by MachineMemoryOperand.
This can cause an assertion failure when LiveDebugValues references a
dead stack object.
It is difficult to craft a test case. -g, va_copy and stack-coloring are
required. I can only reproduce it on ppc32.

[ARM] Favour post inc for MVE loops
We were previously not necessarily favouring postinc for the MVE loads 
and stores, leading to extra code prior to the loop to set up the 
preinc. MVE in general can benefit from postinc (as we don't have 
unrolled loops), and certain instructions like the VLD2's only post-inc 
versions are available.
Differential Revision: https://reviews.llvm.org/D70790

[ARM] MVE VLDn post inc tests. NFC

[ARM] MVE VLDn postinc
This adds Post inc variants of the VLD2/4 and VST2/4 instructions in 
MVE. It uses the same mechanism/nodes as Neon, transforming the 
intrinsic+add pair into a ARMISD::VLD2_UPD, which gets selected to a 
post-inc instruction. The code to do that is mostly taken from the 
existing Neon code, but simplified as less variants are needed.
It also fills in some getTgtMemIntrinsic for the arm.mve.vld2/4 
instrinsics, which allow the nodes to have MMO's, calculated as the full 
length to the memory being loaded/stored.
Differential Revision: https://reviews.llvm.org/D71194

[LLVMgold][test] Fix llvm-nm test after D72658
Differential Revision: https://reviews.llvm.org/D73014

[llvm-mc] - Produce R_X86_64_PLT32 relocation for branches with JCC
opcodes too.
The idea is to produce R_X86_64_PLT32 instead of R_X86_64_PC32 for
branches.
It fixes https://bugs.llvm.org/show_bug.cgi?id=44397.
This patch teaches MC to do that for JCC (jump if condition is met) 
instructions. The new behavior matches modern GNU as. It is similar to
D43383, which did the same for "call/jmp foo", but missed JCC cases.
Differential revision: https://reviews.llvm.org/D72831

[test] Simplify CodeGen/PowerPC/stack-coloring-vararg.mir

[IndVarSimplify][LoopUtils] rewriteLoopExitValues. NFCI
This moves `rewriteLoopExitValues()` from IndVarSimplify to LoopUtils
thus making it a generic loop utility function.  This allows to rewrite
loop exit values by just calling this function without running the whole
IndVarSimplify pass.
We use this in D72714 to rematerialise the iteration count in exit
blocks, so that we can clean-up loop update expressions inside the
hardware-loops later.
Differential Revision: https://reviews.llvm.org/D72602

[llvm-objdump] - Fix the indentation when printing dynamic tags.
We have a bug currently: printed tag names might overlap the value
column. It happens for MIPS now.
This patch adds a logic to calculate the size of indentation on fly to
fix such issues.
Differential revision: https://reviews.llvm.org/D72838

Recommit "[DWARF5][DebugInfo]: Added support for DebugInfo generation
for auto return type for C++ member functions."
Summary: This was reverted in 328e0f3dcac52171b8cdedeaba22c98e7fbb75ea
due to chromium bot failure. This revision addresses that case.
Original commit message: Summary:
   This patch will provide support for auto return type for the C++
member
   functions. Before this return type of the member function is deduced
and
   stored in the DIE.
   This patch includes llvm side implementation of this feature.
    Patch by: Awanish Pandey <Awanish.Pandey@amd.com>
    Reviewers: dblaikie, aprantl, shafik, alok, SouraVX,
jini.susan.george
    Reviewed by: dblaikie
    Differential Revision: https://reviews.llvm.org/D70524

[LoopUtils] Better accuracy for getLoopEstimatedTripCount.
Summary: Current implementation of getLoopEstimatedTripCount returns 1
iteration less than it should. The reason is that in bottom tested loop
first iteration is executed before first back branch is taken. For
example for loop with !{!"branch_weights", i32 1 // taken, i32 1 //
exit} metadata getLoopEstimatedTripCount gives 1 while actual number of
iterations is 2.
Reviewers: Ayal, fhahn
Reviewed By: Ayal
Subscribers: mgorny, hiraditya, zzheng, llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D71990

[test] On Mac, don't try to use result of sysctl command if calling it
failed.
If sysctl is not found at all, let the usual exception propogate so that
the user can fix their env. If it fails because of the permissions
required to read the property then print a warning and continue.
Differential Revision: https://reviews.llvm.org/D72278

[NFC][LoopUtils] Minor change in comment according to review D71990.

[ARM][MVE] Tail-Predication: rematerialise iteration count in exit
blocks
This patch uses helper function rewriteLoopExitValues that is refactored
in D72602 to rematerialise the iteration count in exit blocks, so that
we can clean-up loop update expressions inside the hardware-loops later
in ARMLowOverheadLoops, which is necessary to get actual performance
gains for tail-predicated loops.
Differential Revision: https://reviews.llvm.org/D72714

[lldb/DWARF] Change how we construct a llvm::DWARFContext
Summary: The goal of this patch is two-fold. First, it fixes a
use-after-free in the construction of the llvm DWARFContext. This
happened because the construction code was throwing away the lldb
DataExtractors it got while reading the sections (unlike their llvm
counterparts, these are also responsible for memory ownership). In most
cases this did not matter, because the sections are just slices of the
mmapped file data. But this isn't the case for compressed elf sections,
in which case the section is decompressed into a heap buffer. A similar
thing also happen with object files which are loaded from process
memory.
The second goal is to make it explicit which sections go into the llvm 
DWARFContext -- any access to the sections through both DWARF parsers 
carries a risk of parsing things twice, so it's better if this is a 
conscious decision. Also, this avoids loading completely irrelevant 
sections (e.g. .text). At present, the only section that needs to be 
present in the llvm DWARFContext is the debug_line_str. Using it through 
both APIs is not a problem, as there is no parsing involved.
The first goal is achieved by loading the sections through the existing 
lldb DWARFContext APIs, which already do the caching. The second by 
explicitly enumerating the sections we wish to load.
Reviewers: JDevlieghere, aprantl
Subscribers: lldb-commits
Tags: #lldb
Differential Revision: https://reviews.llvm.org/D72917

[X86][SSE] Add PACKSS SimplifyMultipleUseDemandedBits 'sign bit'
handling.
Attempt to use SimplifyMultipleUseDemandedBits to simplify PACKSS if
we're only after the sign bit.

[clangd] Remove a stale FIXME, NFC.

Add missing tests for parent traversal

Compare traversal for memoization before bound nodes container

[clang][CodeComplete] Propogate printing policy to FunctionDecl
Summary: Printing policy was not propogated to functiondecls when
creating a completion string which resulted in canonical template
parameters like
`foo<type-parameter-0-0>`. This patch propogates printing policy to
those as well.
Fixes https://github.com/clangd/clangd/issues/76
Reviewers: ilya-biryukov
Subscribers: jkorous, arphaman, usaxena95, cfe-commits
Tags: #clang
Differential Revision: https://reviews.llvm.org/D72715

[LV] Vectorizer should adjust trip count in profile information
Summary: Vectorized loop processes VFxUF number of elements in one
iteration thus total number of iterations decreases proportionally. In
addition epilog loop may not have more than VFxUF - 1 iterations. This
patch updates profile information accordingly.
Reviewers: hsaito, Ayal, fhahn, reames, silvas, dcaballe, SjoerdMeijer,
mkuper, DaniilSuchkov
Reviewed By: Ayal, DaniilSuchkov
Subscribers: fedor.sergeev, hiraditya, rkruppe, llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D67905

Fix clang-formatting for recent commits

[lldb/DWARF] Simplify DWARFDebugInfoEntry::LookupAddress
Summary: This method was doing a lot more than it's only caller needed
(DWARFDIE::LookupDeepestBlock) needed, so I inline it into the caller, 
and remove any code which is not actually used. This includes code for 
searching for the deepest function, and the code for working around 
incomplete DW_AT_low_pc/high_pc attributes on a compile unit DIE (modern 
compiler get this right, and this method is called on function DIEs 
anyway).
This also improves our llvm consistency, as llvm::DWARFDebugInfoEntry is 
just a very simple struct with no nontrivial logic.
Reviewers: JDevlieghere, aprantl
Subscribers: lldb-commits
Tags: #lldb
Differential Revision: https://reviews.llvm.org/D72920

Make SymbolFileDWARF::ParseLineTable use std::sort instead of insertion
sort
Summary: Motivation: When setting breakpoints in certain projects line
sequences are frequently being inserted out of order.
Rather than inserting sequences one at a time into a sorted line table,
store all the line sequences as we're building them up and sort and
flatten afterwards.
Reviewers: jdoerfert, labath
Reviewed By: labath
Subscribers: teemperor, labath, mgrang, JDevlieghere, lldb-commits
Tags: #lldb
Differential Revision: https://reviews.llvm.org/D72909

Fix the invisible-traversal to ignore more nodes

[lldb] Don't process symlinks deep inside DWARFUnit
Summary: This code is handling debug info paths starting with
/proc/self/cwd, which is one of the mechanisms people use to obtain
"relocatable" debug info (the idea being that one starts the debugger
with an appropriate cwd and things "just work").
Instead of resolving the symlinks inside DWARFUnit, we can do the same 
thing more elegantly by hooking into the existing Module path remapping 
code. Since llvm::DWARFUnit does not support any similar functionality, 
doing things this way is also a step towards unifying llvm and lldb 
dwarf parsers.
Reviewers: JDevlieghere, aprantl, clayborg, jdoerfert
Subscribers: lldb-commits
Tags: #lldb
Differential Revision: https://reviews.llvm.org/D71770

[lldb] Allow loading of minidumps with no process id
Summary: Normally, on linux we retrieve the process ID from the
LinuxProcStatus stream (which is just the contents of /proc/%d/status
pseudo-file).
However, this stream is not strictly required (it's a breakpad 
extension), and we are encountering a fair amount of minidumps which do 
not have it present. It's not clear whether this is the case with all 
these minidumps, but the two known situations where this stream can be 
missing are:
- /proc filesystem not mounted (or something to that effect)
- process crashing after exhausting (almost) all file descriptors (so
 the minidump writer may not be able to open the /proc file)
Since this is a corner case which will become less and less relevant
(crashpad-generated minidumps should not suffer from this problem), I 
work around this problem by hardcoding the PID to 1 in these cases. The
same thing is done by the gdb plugin when talking to a stub which does
not report a process id (e.g. a hardware probe).
Reviewers: jingham, clayborg
Subscribers: markmentovai, lldb-commits
Tags: #lldb
Differential Revision: https://reviews.llvm.org/D70238

[AArch64][SVE] Extend int_aarch64_sve_ld1_gather_imm
The ACLE distinguishes between the following addressing modes for gather 
loads:
 * "scalar base, vector offset", and
 * "vector base, scalar offset". For the "vector base, scalar offset"
case, the
`int_aarch64_sve_ld1_gather_imm` intrinsic was added in 79f2422d. 
Currently, that intrinsic assumes that the scalar offset is passed as an 
immediate.  As a result, it does not cater for cases where scalar offset 
is stored in a register.
In this patch `int_aarch64_sve_ld1_gather_imm` is extended so that all 
cases are covered:
* `int_aarch64_sve_ld1_gather_imm` is renamed as
 `int_aarch64_sve_ld1_gather_scalar_offset`
* new DAG combine rules are added for GLD1_IMM for scenarios where the
 offset is a non-immediate scalar or an out-of-range immediate
* sve-intrinsics-gather-loads-vector-base.ll is renamed as
 sve-intrinsics-gather-loads-vector-base-imm-offset.ll
* sve-intrinsics-gather-loads-vector-base-scalar-offset.ll is added to
test
 file for non-immediate offsets
Similar changes are made for scatter store intrinsics.
Reviewed By: sdesmalen, efriedma
Differential Revision: https://reviews.llvm.org/D71773

[mlir] Add in-dialect lowering of gpu.all_reduce.
Reviewers: ftynse, nicolasvasilache, herhut
Reviewed By: ftynse, herhut
Subscribers: liufengdb, aartbik, herhut, merge_guards_bot, mgorny,
mehdi_amini, rriddle, jpienaar, burmako, shauheen, antiagainst,
nicolasvasilache, arpith-jacob, mgester, lucyrfox, llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D72129

[llvm-profdata] Fix hint message since argument format has changed
"-sample" option is now changed to "--sample".

[ARM,MVE] Fix confusing MC names for MVE VMINA/VMAXA insns.
Summary: A recent commit accidentally defined names like `MVE_VMAXAs8`
as instances of the multiclass `MVE_VMINA`, and vice versa. This has no 
effect on the test suite, because nothing directly refers to those 
instruction names (the isel patterns are generated in Tablegen using
`!cast<Instruction>(NAME)` inside a lower-level multiclass). But it 
means that `llvm-mc -show-inst` was listing VMAXA as VMINA, and it would
also affect any further draft code gen patches that use those 
instruction ids.
Reviewers: MarkMurrayARM, dmgreen, miyuki, ostannard
Reviewed By: dmgreen
Subscribers: kristof.beyls, hiraditya, llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D73034

[mlir] clarify LangRef wording around control flow in regions
It was unclear what "exiting a region" meant in the existing
formulation. Phrase it in terms of control flow transfer to the
operation enclosing the region.
Discussion:
https://groups.google.com/a/tensorflow.org/d/msg/mlir/73d2O8gjTuA/xVj1KoCTBAAJ

[lldb] Mark the implicit copy constructor as deleted when a move
constructor is provided.
Summary: CXXRecordDecls that have a move constructor but no copy
constructor need to have their implicit copy constructor marked as
deleted (see C++11 [class.copy]p7, p18) Currently we don't do that when
building an AST with ClangASTContext which causes Sema to realise that
the AST is malformed and asserting when trying to create an implicit 
copy constructor for us in the expression:
``` Assertion failed: ((data().DefaultedCopyConstructorIsDeleted ||
needsOverloadResolutionForCopyConstructor())
   && "Copy constructor should not be deleted"), function
setImplicitCopyConstructorIsDeleted, file include/clang/AST/DeclCXX.h,
line 828.
```
In the test case there is a class `NoCopyCstr` that should have its copy
constructor marked as deleted (as it has a move constructor). When we
end up trying to tab complete in the
`IndirectlyDeletedCopyCstr` constructor, Sema realises that the
`IndirectlyDeletedCopyCstr` has no implicit copy constructor and tries
to create one for us. It then realises that
`NoCopyCstr` also has no copy constructor it could find via lookup.
However because we haven't marked the FieldDecl as having a deleted copy
constructor the
`needsOverloadResolutionForCopyConstructor()` returns false and the
assert fails.
`needsOverloadResolutionForCopyConstructor()` would return true if
during the time we added the `NoCopyCstr` FieldDecl to
`IndirectlyDeletedCopyCstr` we would have actually marked it as having a
deleted copy constructor (which would then mark the copy constructor of
`IndirectlyDeletedCopyCstr ` as needing overload resolution and Sema is
happy).
This patch sets the correct mark when we complete our CXXRecordDecls
(which is the time when we know whether a copy constructor has been
declared). In theory we don't have to do this if we had a Sema around
when building our debug info AST but at the moment we don't have this so
this has to do the job for now.
Reviewers: shafik
Reviewed By: shafik
Subscribers: aprantl, JDevlieghere, lldb-commits
Tags: #lldb
Differential Revision: https://reviews.llvm.org/D72694

[SCEV] Swap guards estimation sequence. NFC
Summary: Loop unroll spends a lot of time in SCEVs processing in case
when a function contains hundreds of simple 'for' loops with a quite
complex arrays indexes like
  for (int i = 0; i < 8; ++i) {
   for (int j = 0; j < 32; ++j) {
     C[j*8+i] = B[j*32+i+128] + A[i*64+128];
   }
 }
 for (int i = 0; i < 8; ++i) {
   for (int j = 0; j < 8; ++j) {
     for (int k = 0; k < 32; ++k) {
       D[k*64+i*8+j] = D[k*64+i*8+j] + E[i+16] * C[k*8+j+256];
     }
   }
 }
The patch improves loop unroll speed since isLoopBackedgeGuardedByCond
takes much less time than isLoopEntryGuardedByCond in the edge case.
Reviewers: skatkov, sanjoy, mkazantsev
Reviewed By: sanjoy
Subscribers: fhahn, hiraditya, javed.absar, llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D72929

[InstSimplify] fold select of vector constants that include undef
elements
As mentioned in D72643, we'd like to be able to assert that any select 
of equivalent constants has been removed before we're deep into
InstCombine.
But there's a loophole in that assertion for vectors with undef elements 
that don't match exactly.
This patch should close that gap. If we have undefs, we can't safely 
propagate those unless both constants elements for that lane are undef.
Differential Revision: https://reviews.llvm.org/D72958

[lldb][NFC] Add test for iterator invalidation during code completion.

[ms] [llvm-ml] Add placeholder for llvm-ml, based on llvm-mc
As discussed on the mailing list, I plan to introduce an ml-compatible
MASM assembler as part of providing more of the Windows build tools.
This will be similar to llvm-mc, but with different command-line
parameters.
This placeholder is purely a stripped-down version of llvm-mc; we'll
eventually add support for the Microsoft-style command-line flags, and
back it with a MASM parser.
Relanding this revision after fixing ARM-compatibility issues.
Reviewers: rnk, thakis, RKSimon
Reviewed By: thakis, RKSimon
Differential Revision: https://reviews.llvm.org/D72679

[ARM][MVE][Intrinsics] Take abs() of VMINNMAQ, VMAXNMAQ intrinsics'
first arguments.
Summary: Fix VMINNMAQ, VMAXNMAQ intrinsics; BOTH arguments have the
absolute values taken.
Reviewers: dmgreen, simon_tatham
Subscribers: kristof.beyls, hiraditya, cfe-commits, llvm-commits
Tags: #clang, #llvm
Differential Revision: https://reviews.llvm.org/D72830

[Alignment][NFC] Use Align with CreateElementUnorderedAtomicMemCpy
Summary: This is patch is part of a series to introduce an Alignment
type. See this thread for context:
http://lists.llvm.org/pipermail/llvm-dev/2019-July/133851.html See this
patch for the introduction of the type: https://reviews.llvm.org/D64790
Reviewers: courbet, nicolasvasilache
Subscribers: hiraditya, jfb, mehdi_amini, rriddle, jpienaar, burmako,
shauheen, antiagainst, csigg, arpith-jacob, mgester, lucyrfox, herhut,
liufengdb, llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D73041

[libomptarget] Implement smid for amdgcn
Summary:
[libomptarget] Implement smid for amdgcn
Implementation is in a new file as it uses an intrinsic with complicated
encoding that warranted substantial comments.
Reviewers: jdoerfert, grokos, ABataev, ronlieb
Reviewed By: jdoerfert
Subscribers: jvesely, mgorny, openmp-commits
Tags: #openmp
Differential Revision: https://reviews.llvm.org/D72956

Fix build - removing legacy target reference.

[llvm-exegesis][NFC] Disassociate snippet generators from benchmark
runners
The addition of `inverse_throughput` mode highlighted the disjointedness 
of snippet generators and benchmark runners because it used the
`UopsSnippetGenerator` with the  `LatencyBenchmarkRunner`. To keep the
code consistent tie the snippet generators to 
parallelization/serialization rather than their benchmark runners.
Renaming `LatencySnippetGenerator` -> `SerialSnippetGenerator`. Renaming
`UopsSnippetGenerator` -> `ParallelSnippetGenerator`.
Differential Revision: https://reviews.llvm.org/D72928

[gn build] Port 24b7b99b7d6

[InstCombine] form copysign from select of FP constants (PR44153)
This should be the last step needed to solve the problem in the 
description of PR44153: https://bugs.llvm.org/show_bug.cgi?id=44153
If we're casting an FP value to int, testing its signbit, and then 
choosing between a value and its negated value, that's a complicated way
of saying "copysign":
(bitcast X) <  0 ? -TC :  TC --> copysign(TC,  X)
Differential Revision: https://reviews.llvm.org/D72643

[FileCheck] Clean and improve unit tests
Summary: Clean redundant unit test checks (codepath already tested
elsewhere) and add a few missing checks for existing numeric
substitution and match logic.
Reviewers: jhenderson, jdenny, probinson, grimar, arichardson, rnk
Reviewed By: jhenderson
Subscribers: llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D72912

Add support for Linux/Musl ABI
Differential revision: https://reviews.llvm.org/D72701
The patch adds a new option ABI for Hexagon. It primary deals with the
way variable arguments are passed and is use in the Hexagon Linux Musl 
environment.
If a callee function has a variable argument list, it must perform the 
following operations to set up its function prologue:
  1. Determine the number of registers which could have been used for
passing
    unnamed arguments. This can be calculated by counting the number of
    registers used for passing named arguments. For example, if the
callee
    function is as follows:
         int foo(int a, ...){ ... }
     ... then register R0 is used to access the argument ' a '. The
registers
    available for passing unnamed arguments are R1, R2, R3, R4, and R5.
  2. Determine the number and size of the named arguments on the stack.
  3. If the callee has named arguments on the stack, it should copy all
of these
    arguments to a location below the current position on the stack, and
the
    difference should be the size of the register-saved area plus
padding
    (if any is necessary).
     The register-saved area constitutes all the registers that could
have
    been used to pass unnamed arguments. If the number of registers
forming
    the register-saved area is odd, it requires 4 bytes of padding; if
the
    number is even, no padding is required. This is done to ensure an
8-byte
    alignment on the stack.  For example, if the callee is as follows:
       int foo(int a, ...){ ... }
     ... then the named arguments should be copied to the following
location:
       current_position - 5 (for R1-R5) * 4 (bytes) - 4 (bytes of
padding)
     If the callee is as follows:
        int foo(int a, int b, ...){ ... }
     ... then the named arguments should be copied to the following
location:
        current_position - 4 (for R2-R5) * 4 (bytes) - 0 (bytes of
padding)
  4. After any named arguments have been copied, copy all the registers
that
    could have been used to pass unnamed arguments on the stack. If the
number
    of registers is odd, leave 4 bytes of padding and then start copying
them
    on the stack; if the number is even, no padding is required. This
    constitutes the register-saved area. If padding is required, ensure
    that the start location of padding is 8-byte aligned.  If no padding
is
    required, ensure that the start location of the on-stack copy of the
    first register which might have a variable argument is 8-byte
aligned.
  5. Decrement the stack pointer by the size of register saved area plus
the
    padding.  For example, if the callee is as follows:
        int foo(int a, ...){ ... } ;
     ... then the decrement value should be the following:
        5 (for R1-R5) * 4 (bytes) + 4 (bytes of padding) = 24 bytes
     The decrement should be performed before the allocframe
instruction.
    Increment the stack-pointer back by the same amount before returning
    from the function.

[clangd] Avoid redundant testcases in rename unittest, NFC.
Reviewers: kadircet
Subscribers: ilya-biryukov, MaskRay, jkorous, arphaman, usaxena95,
cfe-commits
Tags: #clang
Differential Revision: https://reviews.llvm.org/D73035

clang-format: [JS] fix `??` opreator wrapping.
Summary: clang-format currently treats the nullish coalescing operator
`??` like the ternary operator. That causes multiple nullish terms to be
each indented relative to the last `??`, as they would in a ternary.
The `??` operator is often used in chains though, and as such more 
similar to other binary operators, such as `||`. So to fix the indent, 
set its token type to `||`, so it inherits the same treatment.
This opens up the question of operator precedence. However, `??` is 
required to be parenthesized when mixed with `||` and `&&`, so this is 
not a problem that can come up in syntactically legal code.
Reviewers: krasimir
Subscribers: cfe-commits
Tags: #clang
Differential Revision: https://reviews.llvm.org/D73026

[OPENMP]Fix PR44578: crash in target construct with captured global.
Target regions have implicit outer region which may erroneously capture 
some globals when it should not. It may lead to a compiler crash at the 
compile time.

[FileCheck] Make Match unittest more flexible
Summary: FileCheck's Match unittest needs updating whenever some call to 
initNextPattern() is inserted before its final block of checks. This 
commit change usage of LineNumber inside the Tester object so that the 
line number of the current pattern can be queries, thereby making the 
Match test more solid.
Reviewers: jhenderson, jdenny, probinson, grimar, arichardson, rnk
Reviewed By: jhenderson
Subscribers: llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D72913

[SelectionDAG] GetDemandedBits - fallback to
SimplifyMultipleUseDemandedBits by default.
First step towards removing SelectionDAG::GetDemandedBits entirely since
it so similar to SimplifyMultipleUseDemandedBits anyhow.

[clang-tidy] Add check for CERT-OOP57-CPP
Summary: This is a very basic warning implementation of [[
https://wiki.sei.cmu.edu/confluence/display/cplusplus/OOP57-CPP.+Prefer+special+member+functions+and+overloaded+operators+to+C+Standard+Library+functions
| Prefer special member functions and overloaded operators to C Standard
Library functions ]]
It absolutely needs some fine tuning though.
Reviewers: alexfh, hokein, aaron.ballman, JonasToth
Reviewed By: aaron.ballman
Subscribers: merge_guards_bot, Eugene.Zelenko, mgorny, xazax.hun,
cfe-commits
Tags: #clang, #clang-tools-extra
Differential Revision: https://reviews.llvm.org/D72488

[gn build] Port a42c3eb599c

[llvm-exegesis] Remove unused variable after D72928

[lldb/Util] Add a utility to run transparently capture and replay tests.
This patch introduces a small new utility (lldb-repro) to transparently 
capture and replay debugger sessions through the command line driver. 
Its used to test the reproducers by running the test suite twice.
During the first run, it captures a reproducer for every lldb invocation 
and saves it to a well-know location derived from the arguments and 
current working directory. During the second run, the test suite is run 
again but this time every invocation of lldb replays the previously 
recorded session.
Differential revision: https://reviews.llvm.org/D72823

[lldb/Test] Check that attribute exists before comparing its value

[OpenMP] affinity little fix for FreeBSD
- pthread affinity np has different semantic than sched affinity
counterpart. On success returns strictly 0.
Reviewers: chandlerc, AndreyChurbanov, jdoerfert
Reviewed By: jdoerfert
Differential Revision: https://reviews.llvm.org/D72132

[lldb/IOHandler] Improve synchronization between IO handlers.
The way the IO handlers are currently managed by the debugger is wrong.
The implementation lacks proper synchronization between RunIOHandlerSync
and RunIOHandlers. The latter is meant to be run by the "main thread",
while the former is meant to be run synchronously, potentially from a
different thread.
Imagine a scenario where RunIOHandlerSync is called from a different
thread than RunIOHandlers. Both functions manipulate the debugger's
IOHandlerStack. Although the push and pop operations are synchronized,
the logic to activate, deactivate and run IO handlers is not.
While investigating PR44352, I noticed some weird behavior in the
Editline implementation. One of its members (m_editor_status) was
modified from another thread. This happened because the main thread,
while running RunIOHandlers ended up execution the IOHandlerEditline
created by the breakpoint callback thread. Even worse, due to the lack
of synchronization within the IO handler implementation, both threads
ended up executing the same IO handler.
Most of the time, the IO handlers don't need to run synchronously. The 
exception is sourcing commands from external files, like the .lldbinit
file.
I've added a (recursive) mutex to prevent another thread from messing
with the IO handlers wile another thread is running one synchronously.
It has to be recursive, because we might have to source another file
when encountering a command source in the original file.
Differential revision: https://reviews.llvm.org/D72748

[clangd] Fix DocumentOutline for concepts
Summary: Fixes https://github.com/clangd/clangd/issues/256
Reviewers: kbobyrev
Subscribers: ilya-biryukov, MaskRay, jkorous, arphaman, usaxena95,
cfe-commits
Tags: #clang
Differential Revision: https://reviews.llvm.org/D73056

[lldb/Docs] Add lldb-x86_64-fedora to the CI page

AMDGPU/GlobalISel: Add documentation for RegisterBankInfo
Document some high level strategies that should be used for register 
bank selection. The constant bus restriction section hasn't actually 
been implemented yet.

[mlir] Generalize broadcastable trait operands
Summary: Generalize broadcastable trait to variadic operands. Update the 
documentation that still talked about element type as part of 
broadcastable trait (that bug was already fixed). Also rename 
Broadcastable to ResultBroadcastableShape to be more explicit that the 
trait affects the result shape (it is possible for op to allow 
broadcastable operands but not have result shape that is broadcast 
compatible with operands).
Doing some intermediate work to have getBroadcastedType take an optional 
elementType as input and use that if specified, instead of the common 
element type of type1 and type2 in this function.
Differential Revision: https://reviews.llvm.org/D72559

[NFC] small rename of private member in InlineCost.cpp
Summary: Follow-up from https://reviews.llvm.org/D71733. Also moved an 
initialization to the base class, where it belonged in the first place.
Reviewers: eraman, davidxl
Reviewed By: davidxl
Subscribers: hiraditya, haicheng, llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D72949

Fix printer for llvm.addressof symbol name that need escaping
Differential Revision: https://reviews.llvm.org/D73065

[Hexagon] Add support for Hexagon/HVX v67 ISA

AMDGPU: Partially merge indirect register write handling
a785209bc2fb switched to using a pseudos instead of manually tying 
operands on the regular instruction. The VGPR indexing mode path should
have the same problems that change attempted to avoid, so these should
use the same strategy.
Use a single pseudo for the VGPR indexing mode and movreld paths, and 
expand it based on the subtarget later. These have essentially the same
constraints, reading the index from m0.
Switch from using an offset to the subregister index directly, instead 
of computing an offset and re-adding it back. Also add missing pseudos 
for existing register class sizes.

AMDGPU: Prepare to use scalar register indexing
Define pseudos mirroring the the VGPR indexing ones, and adjust the 
operands in the s_movrel* instructions to avoid the result def.

AMDGPU: Cleanup and generate 64-bit div tests
Split out r600 tests, and try to be more consistent with coverage. Cover
a few more cases for 24-bit optimization and constants.

[lld][ELF] Don't apply --fix-cortex-a53-843419 to relocatable links.
The code doesn't apply the fix correctly to relocatable links. I could 
try to fix the code that applies the fix, but it's pointless: we don't 
actually know what the offset will be in the final executable. So just 
ignore the flag for relocatable links.
Issue discovered building Android.
Differential Revision: https://reviews.llvm.org/D72968

[AsmPrinter] Don't emit __patchable_function_entries entry if
"patchable-function-entry"="0"
Add improve tests

Revert "PR17164: Change clang's default behavior from
-flax-vector-conversions=all to -flax-vector-conversions=integer."
This patch broke the Sanitizer buildbots. Please see the commit's 
differential revision for more information
(https://reviews.llvm.org/D67678).
This reverts commit b72a8c65e4e34779b6bc9e466203f553f5294486.

AMDGPU: Don't create weird sized integers
There's no reason to introduce a new, unnaturally sized value here. This
has a chance to produce worse code with legalization. Avoids regression
in a future patch.

AMDGPU: Generate test checks
These weren't much different than copied output anyway.

Revert "[libc++] Optimize / partially inline basic_string copy
constructor"
This reverts commit a8a9c8e0a11abc9ed4ed78fed528334371fedf87.
There are multiple reported failures caused by this change. Each failure
is really weird, but it makes sense to revert while investigating.

[lld][RISCV] Print error when encountering R_RISCV_ALIGN
Summary: Unlike R_RISCV_RELAX, which is a linker hint, R_RISCV_ALIGN
requires the support of the linker even when ignoring all R_RISCV_RELAX
relocations. This is because the compiler emits as many NOPs as may be
required for the requested alignment, more than may be required
pre-relaxation, to allow for the target becoming more unaligned after
relaxing earlier sequences. This means that the target is often not
initially aligned in the object files, and so the R_RISCV_ALIGN
relocations cannot just be ignored. Since we do not support linker
relaxation, we must turn these into errors.
Reviewers: ruiu, MaskRay, espindola
Reviewed By: MaskRay
Subscribers: grimar, Jim, emaste, arichardson, asb, rbar, johnrusso,
simoncook, sabuasal, niosHD, kito-cheng, shiva0217, zzheng,
edward-jones, rogfer01, MartinMosbeck, brucehoult, the_o, rkruppe, PkmX,
jocewei, psnobl, benna, lenary, s.egerton, pzheng, sameer.abuasal,
apazos, luismarques, llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D71820

[llvm-objcopy][ELF] Allow setting SHF_EXCLUDE flag for ELF sections
Summary: This patch adds support for setting SHF_EXCLUDE flag for ELF
sections.
Reviewers: jhenderson, grimar, MaskRay, mstorsjo, espindola, alexshap,
rupprecht
Reviewed By: jhenderson, MaskRay
Subscribers: emaste, abrachet, llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D72128

AMDDGPU/GlobalISel: Fix RegBankSelect for llvm.amdgcn.ps.live

[clangd] Fix rename for explicit destructor calls
When triggering rename of the class name in the code with explicit
destructor calls, rename fails. Consider the following piece of code:
``` class Foo;
...
Foo f; f.~/*...*/Foo();
```
`findExplicitReferences` will report two `ReferenceLoc` for destructor
call: one is comming from `MemberExpr` (i.e. destructor call itself) and
would point to the tilde:
``` f.~/*...*/Foo();
 ^
```
And the second one is pointing to the typename and is coming from
`TypeLoc`.
``` f.~/*...*/Foo();
         ^
```
This causes rename to produce incorrect textual replacements. This patch 
updates `MemberExpr` handler to detect destructor calls and prevents it 
from reporting a duplicate reference.
Resolves: https://github.com/clangd/clangd/issues/236
Reviewers: kadircet, hokein
Differential Revision: https://reviews.llvm.org/D72638

Revert "[MachO] Add a test for detecting reserved unit length."
This change broke the UBSan buildbots. More information available in the 
original Phabricator review: https://reviews.llvm.org/D72695
This reverts commit fcc08aa835de1e0c1f3e7e479917575e55433b68.

[AMDGPU] Fix -Wunused-variable after
e5823bf806ca9fa6f87583065b3898a2edabce57

[MC] Improve a report_fatal_error

[RISCV] Pass target-abi via module flag metadata
Reviewers: lenary, asb
Reviewed By: lenary
Tags: #clang
Differential Revision: https://reviews.llvm.org/D72755

Revert "[AMDGPU] Invert the handling of skip insertion."
This reverts commit 0dc6c249bffac9f23a605ce4e42a84341da3ddbd.
The commit is reported to cause a regression in piglit/bin/glsl-vs-loop
for Mesa.

[gn build] Port a80291ce10b

[MLIR] LLVM Dialect: add llvm.cmpxchg and improve llvm.atomicrmw custom
parser
Summary: Add a `llvm.cmpxchg` op as a counterpart to LLVM IR's `cmpxchg`
instruction. Note that the `weak`, `volatile`, and `syncscope`
attributes are not yet supported.
This will be useful for upcoming parallel versions of affine.for and
generally for reduction-like semantics (especially for reductions that
can't make use of `atomicrmw`, e.g. `fmax`).
Reviewers: ftynse, nicolasvasilache
Reviewed By: ftynse
Subscribers: merge_guards_bot, jfb, mehdi_amini, rriddle, jpienaar,
burmako, shauheen, antiagainst, arpith-jacob, mgester, lucyrfox,
liufengdb, llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D72995

[ARM][MVE] Enable masked scatter
Extends the gather/scatter pass in MVEGatherScatterLowering.cpp to 
enable the transformation of masked scatters into calls to MVE's masked 
scatter intrinsic.
Differential Revision: https://reviews.llvm.org/D72856

Reapply: [MachO] Add a test for detecting reserved unit length.
The test in the origin patch did not create a __debug_str section. An
UBSan check triggered when the corresponding pointer was dereferenced.
Differential Revision: https://reviews.llvm.org/D72695
This reapplies fcc08aa835de1e0c1f3e7e479917575e55433b68 which was
reverted in b16f82ad3b095070729cde2873bd3a2e8ab35c0e.

[LLD][ELF] Add support for INPUT_SECTION_FLAGS
The INPUT_SECTION_FLAGS linker script command is used to constrain the 
section pattern matching to sections that match certain combinations of 
flags.
There are two ways to express the constraint. withFlags: Section must
have these flags. withoutFlags: Section must not have these flags.
The syntax of the command is: INPUT_SECTION_FLAGS '(' sect_flag_list ')' 
sect_flag_list: NAME
| sect_flag_list '&' NAME
Where NAME matches a section flag name such as SHF_EXECINSTR, or the 
integer value of a section flag. If the first character of NAME is !
then it means must not contain flag.
We do not support the rare case of { INPUT_SECTION_FLAGS(flags) filespec
} where filespec has no input section description like (.text).
As an example from the ld man page: SECTIONS {
 .text : { INPUT_SECTION_FLAGS (SHF_MERGE & SHF_STRINGS) *(.text) }
 .text2 :  { INPUT_SECTION_FLAGS (!SHF_WRITE) *(.text) }
}
.text will match sections called .text that have both the SHF_MERGE and 
SHF_STRINGS flag.
.text2 will match sections called .text that don't have the SHF_WRITE
flag.
The flag names accepted are the generic to all targets and
SHF_ARM_PURECODE as it is very useful to filter all the pure code
sections into a single program header that can be marked execute never.
fixes PR44265
Differential Revision: https://reviews.llvm.org/D72756

Regenerate rotated uxt tests

[TargetLowering] SimplifyDemandedBits - Pull out InDemandedMask variable
to ISD::SHL. NFCI.
Matches ISD::SRA + ISD::SRL variants.

[llvm-exegesis] Add support for AVX512 explicit rounding operands.
Reviewers: gchatelet
Subscribers: tschuett, mstojanovic, llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D73083

[DAG] Fold extract_vector_elt (scalar_to_vector), K to undef (K != 0)
This was unconditionally folding this to the source operand, even if the
access was out of bounds. Use undef instead of the extract is not the
first element.
This helps with some cases where 3-vectors are legalized and avoids
processing the 4th component.
Original Patch by: arsenm (Matt Arsenault)
Differential Revision: https://reviews.llvm.org/D51589

[llvm-readelf][llvm-readobj] - Fix the indentation when printing dynamic
tags.
This change is similar to one made for llvm-objdump in D72838.
llvm-readelf/llvm-readobj tools do not align the "Name/Value" column
properly. This patch adds a logic to calculate the size of indentation
on fly to fix such issues.
Differential revision: https://reviews.llvm.org/D72843

[analyzer] Enable PlacementNewChecker by default

[ELF] Refactor uses of getInputSections to improve efficiency NFC
Add new method getFirstInputSection and use instead of getInputSections 
where appropriate to avoid creation of an unneeded vector of input 
sections.
Differential Revision: https://reviews.llvm.org/D73047

[lldb][NFC] Convert LLDB_LOGF to LLDB_LOG in ClangASTSource.cpp

[llvm-exegesis] Fix support for LEA64_32r.
Summary: Add unit test to show the issue: We must select an *aliasing*
output register, not the exact register.
Reviewers: gchatelet
Subscribers: tschuett, mstojanovic, llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D73095

Create a gpu.module operation for the GPU Dialect.
Summary: This is based on the use of code constantly checking for an
attribute on a model and instead represents the distinct operaion with a
different op. Instead, this op can be used to provide better filtering.
Reverts "Revert "[mlir] Create a gpu.module operation for the GPU
Dialect.""
This reverts commit ac446302ca4145cdc89f377c0c364c29ee303be5 after 
fixing internal Google issues.
This additionally updates ROCDL lowering to use the new gpu.module.
Reviewers: herhut, mravishankar, antiagainst, nicolasvasilache
Subscribers: jholewinski, mgorny, mehdi_amini, jpienaar, burmako,
shauheen, csigg, arpith-jacob, mgester, lucyrfox, aartbik, liufengdb,
llvm-commits, mravishankar, rriddle, antiagainst, bkramer
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D72921

[lldb] Use llvm::stable_sort in Line
This addresses some post-commit feedback on D72909.

[Alignment][NFC] Use Align with CreateMaskedLoad
Summary: This is patch is part of a series to introduce an Alignment
type. See this thread for context:
http://lists.llvm.org/pipermail/llvm-dev/2019-July/133851.html See this
patch for the introduction of the type: https://reviews.llvm.org/D64790
Reviewers: courbet
Subscribers: hiraditya, cfe-commits, llvm-commits
Tags: #clang, #llvm
Differential Revision: https://reviews.llvm.org/D73087

[llvm-readobj] - Remove rpath.test.
rpath.test checks that DT_RPATH is dumped.
We have dynamic-tags.test that tests all dynamic tags and it is better,
because also checks llvm-readelf and does not use precompiled binaries.
Differential revision: https://reviews.llvm.org/D73093

[Alignment][NFC] Use Align with CreateElementUnorderedAtomicMemMove
Summary: This is patch is part of a series to introduce an Alignment
type. See this thread for context:
http://lists.llvm.org/pipermail/llvm-dev/2019-July/133851.html See this
patch for the introduction of the type: https://reviews.llvm.org/D64790
Reviewers: courbet
Subscribers: hiraditya, jfb, llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D73050

AMDGPU/GlobalISel: Add some baseline tests for unmerge legalization

[clang-tidy] New check: bugprone-misplaced-pointer-arithmetic-in-alloc
Finds cases where an integer expression is added to the result of a
memory allocation function instead of its argument.
Differential Revision: https://reviews.llvm.org/D71001

[gn build] Port fccd0da5ee6

[lldb/DWARF] Fix a leak in line table construction
We were creating a bunch of LineSequence objects but never deleting 
them.
This fixes the leak and changes the code to use std::unique_ptr, to make 
it harder to make the same mistake again.

[lldb/breakpad] Use new line table constructor
The old construction method can be quadratic for some inputs. This 
approach guarantees a reasonable performance.

[TargetLowering] SimplifyDemandedBits ANY_EXTEND/ANY_EXTEND_VECTOR_INREG
multi-use handling
Call SimplifyMultipleUseDemandedBits to peek through extended source
args with multiple uses

[clangd] Capture the missing injected class names in
findExplicitReferences.
Summary: Fixes https://github.com/clangd/clangd/issues/237.
Reviewers: kadircet, kbobyrev
Subscribers: ilya-biryukov, MaskRay, jkorous, arphaman, usaxena95,
cfe-commits
Tags: #clang
Differential Revision: https://reviews.llvm.org/D73088

[X86] combineBT - use SimplifyDemandedBits instead of GetDemandedBits
Another step towards removing SelectionDAG::GetDemandedBits entirely

[SelectionDAG] GetDemandedBits - remove ANY_EXTEND handling
Rely on SimplifyMultipleUseDemandedBits fallback instead.

[PowerPC][NFC] Reclaim TSFlags bit 6
We removed UseVSXReg flag in https://reviews.llvm.org/D58685 But we did
not reclain the bit 6 it was assigned, this will become confusing and a
hole later.. We should reclaim it as early as possible before new bits.
Reviewed By: sfertile
Differential Revision: https://reviews.llvm.org/D72649

Make dropTriviallyDeadConstantArrays not quadratic
Only look at the operands of dead constant arrays instead of all 
constant arrays again.

[TargetLowering] SimplifyDemandedBits ISD::SRA multi-use handling
Call SimplifyMultipleUseDemandedBits to peek through extended source
args with multiple uses

[ARM] Follow AACPS standard for volatile bit-fields access width
Summary: This patch resumes the work of D16586. According to the AAPCS,
volatile bit-fields should be accessed using containers of the widht of
their declarative type. In such case:
``` struct S1 {
 short a : 1;
}
``` should be accessed using load and stores of the width
(sizeof(short)), where now the compiler does only load the minimum
required width (char in this case). However, as discussed in D16586, 
that could overwrite non-volatile bit-fields, which conflicted with C
and C++ object models by creating data race conditions that are not part
of the bit-field, e.g.
``` struct S2 {
 short a;
 int  b : 16;
}
``` Accessing `S2.b` would also access `S2.a`.
The AAPCS Release 2019Q1.1
(https://static.docs.arm.com/ihi0042/g/aapcs32.pdf) section 8.1 Data
Types, page 35, "Volatile bit-fields - preserving number and width of
container accesses" has been updated to avoid conflict with the C++
Memory Model. Now it reads in the note:
``` This ABI does not place any restrictions on the access widths of
bit-fields where the container overlaps with a non-bit-field member.
This is because the C/C++ memory model defines these as being separate 
memory locations, which can be accessed by two threads
simultaneously. For this reason, compilers must be permitted to use a 
narrower memory access width (including splitting the access
into multiple instructions) to avoid writing to a different memory
location.
```
I've updated the patch D16586 to follow such behavior by verifying that
we only change volatile bit-field access when:
- it won't overlap with any other non-bit-field member
- we only access memory inside the bounds of the record
Regarding the number of memory accesses, that should be preserved, that
will be implemented by D67399.
Reviewers: rsmith, rjmccall, eli.friedman, ostannard
Subscribers: ostannard, kristof.beyls, cfe-commits, carwil, olista01
Tags: #clang
Differential Revision: https://reviews.llvm.org/D72932

Revert "[ARM] Follow AACPS standard for volatile bit-fields access
width"
This reverts commit 6a24339a45246b66bd3de88cc9c6a5b5e77c0645. Submitted
using ide button by mistake

[RISCV] Check the target-abi module flag matches the option
Reviewers: lenary, asb
Reviewed By: lenary
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D72768

[clangd] Drop returntype/type when hovering over type-ish names
Summary: Some names, e.g. constructor/destructor/conversions, already
contain the type info, no need to duplicate them in the hoverinfo.
Fixes https://github.com/clangd/clangd/issues/252
Reviewers: sammccall, ilya-biryukov
Subscribers: MaskRay, jkorous, arphaman, usaxena95, cfe-commits
Tags: #clang
Differential Revision: https://reviews.llvm.org/D73110

Update spelling of {analyze,insert,remove}Branch in strings and comments
These names have been changed from CamelCase to camelCase, but there
were many places (comments mostly) that still used the old names.
This change is NFC.

[Clang] Un-break scan-build after integrated-cc1 change
Differential Revision: https://reviews.llvm.org/D72982

[mlir][spirv] Simplify scalar type size calculation.
Simplify scalar type size calculation and reject boolean memrefs.
Differential Revision: https://reviews.llvm.org/D72999

[libcxx] Support Python 3.8 in the test suite
Summary: `platform.linux_distribution()` has been deprecated in Python
3.5 and removed in Python 3.8.
Reviewers: bcain, bcraig, jroelofs, EricWF, mclow.lists, ldionne
Reviewed By: jroelofs
Subscribers: dexonsmith, christof, ldionne, libcxx-commits
Tags: #libc
Differential Revision: https://reviews.llvm.org/D72501