Differential Revision: https://reviews.llvm.org/D156634

Mostly the same as `and`. We also have a check for a useless
`llvm.ptrmask` if the ptr is already known aligned.

Differential Revision: https://reviews.llvm.org/D156633

Differential Revision: https://reviews.llvm.org/D156632

Do not match on illegal destination blocks. Also apply some minor
cleanups.

TODO: We should add region/block argument type conversions to properly
address this.

Issue: https://github.com/llvm/llvm-project/issues/70813

The corresponding function definition was removed by:

  commit 3787ee45
  Author: Nick Desaulniers <ndesaulniers@google.com>
  Date:   Tue Jun 8 08:57:12 2021 -0700

Missed test case in experimental target, which was not covered by pre-merge checks.

…r operation

Reland 3686a0b6 after fixing an exposed miscompile in #68840

Differential Revision: https://reviews.llvm.org/D159140

MachProcess has a MachTask as an ivar. In the MachProcess dtor, we call
MachTask::Clear() to clear its state, before running the dtor of all our
ivars, including the MachTask one.

When we attach on darwin, MachProcess calls
MachTask::StartExceptionThread which does the task_for_pid and then
starts a thread to listen for mach messages. Then MachProcess calls
ptrace(PT_ATTACHEXC). If that ptrace() fails, MachProcess will call
MachTask::Clear. But the exception thread is now up & running and is not
stopped; its ivars will be reset by the Clear() method, and its object
will be freed after the dtor runs.

Actually eliciting a crash in this scenario is very timing sensitive; I
hand-modified debugserver to fail to PT_ATTACHEXC trying to simulate it
on my desktop and was unable. But looking at the source, and an
occasional crash report we've received, it's clear that this is
possible.

rdar://117521198

According to https://developer.apple.com/support/xcode/, quite a few of
our availability macros don't do anything anymore, so we might as well
remove them to clean up the code a bit.

If you build with dynamic_hsa, the symbol is known and compilation
succeeds. If you then run with a slightly older libhsa, this argument is
not recognised and an error returned. I'd rather the program runs with a
misleading omp wtime than refuses to run at all.

zlib.

Not everyone wants to checkout from `git`. Tested with and without the
env var.

Revert "Reland "[clang][Sema] Use original template pattern when declaring implicit deduction guides for nested template classes" (#69676)"

This reverts commit f4183197.

Failing test case: https://github.com/llvm/llvm-project/pull/69676#issuecomment-1789255366

looks like there may be some missing testing here.

Using GCNDownwardRPTracker or GCNUpwardRPTracker the pass collects register pressure values for a function and prints these values next to instructions. Output can be used to generate Filecheck rules in mir tests.

Opaque ptr cleanup effort.

This makes it easier to write .sh.cpp tests that perform multiple clang-verify checks in the same test.

- Document legacy ops lowered by `convert-func-to-llvm` and link it to a
GH issue
- Document the need for bufferization before `convert-linalg-to-loops`
- Document the ops lowered by `expand-strided-metadata`.

Needed for -riscv-experimental-rv64-legal-i32 and probably GISel.

Opaque ptr cleanup effort. NFC.

Co-authored-by: Sylvestre Ledru <sylvestre@debian.org>

Do not issue a hard error when the function in acc routine directive is
not present in the current translation unit. Only issue a warning.

When SI_PC_ADD_REL_OFFSET is expanded to S_GETPC/S_ADD/S_ADDC, the
GlobalAddress operands have to be adjusted by 4 or 12 bytes to account
for the offset from the end of the S_GETPC instruction to the literal
operands. Do this all in SIInstrInfo::expandPostRAPseudo instead of
duplicating the adjustment code in both AMDGPULegalizerInfo and
SITargetLowering. NFCI.

This is essentially a revert of
1ed71083. It is safe to use the
pull_request_target event for pr-subscriber, because it does not
checkout any code from the pull request branch.

We started going over our API limits and suspect this was the cause.
For now, we'll run it once a day while we sort this out.

Constant materialization can use bset x0, 11 to create 2048.

This is essentially a revert of
91fdb209. It is safe to use the
pull_request_target event for new-prs, because it does not checkout any
code from the pull request branch.

The last use was removed by:

  commit 18d9f7eb
  Author: Johannes Doerfert <johannes@jdoerfert.de>
  Date:   Wed Jul 5 15:35:24 2023 -0700

There is no PIC support for -mcmodel=large

(https://github.com/ARM-software/abi-aa/blob/main/sysvabi64/sysvabi64.rst)
and Clang recently rejects -mcmodel= with PIC (#70262).

The current backend code assumes that the large code model is non-PIC.
This patch adds `!getTargetMachine().isPositionIndependent()` conditions
to clarify that the support is non-PIC only. In addition, add some tests
as change detectors in case PIC large code model is supported in the
future.

If other front-ends/JITs use the large code model with PIC, they will
get small code model code sequence, instead of potentially-incorrect
MOVZ/MOVK sequence, which is only suitable for non-PIC. The sequence
will cause text relocations using ELF linkers.

(The small code model code sequence is usually sufficient as ADRP+ADD or
ADRP+LDR targets [-2**32,2**32), which has a doubled range of x86-64
R_X86_64_REX_GOTPCRELX/R_X86_64_PC32 [-2**32,2**32).)

LoopFlatten uses IndVars mechanics to widen induction variables, but then
fails to cleanup the dead instructions returned via the API.  This isn't
a functional problem, but means that this test is highly sensative to
indvars internals in an unhelpful way.  Use DCE to "normalize" the test
output to avoid false positives in a later change.

[clang][modules] Don't prevent translation of FW_Private includes when explicitly building FW (#70714)

We prevent translating `#include <FW/PrivateHeader.h>` into an import of
FW_Private when compiling the implementation of FW or FW_Private. This
is specified via `-fmodule-name=` on the TU command line (used to be
`-fmodule-implementation-of`).

This logic is supposed to only kick in when imported directly from a TU,
but it currently also kicks in when compiling the public FW module
explicitly (since it also has `-fmodule-name=` on the command line).

This patch makes sure this logic only kicks in for the case that used to
be `-fmodule-implementation-of` (for the TU), and not for all
`-fmodule-name=` cases (especially for the explicit compile of a
module).

rdar://101051277; related: rdar://37500098&38434694

The compute and data constructs implement getNumDataOperands and
getDataOperand. The acc.loop operation similarly has multiple data
operands - thus it makes sense to expose them the same way.

For loop, only private and reduction operands are exposed this way.
Technically, acc.loop also holds cache operands - but these are hints
not a data attribute.