To help better test the effects of D136478

The type parameter we used to pass to call() was unused. Use the same
implementation for void and value-returning function calls.

Remove the double Call() implementation to reduce code duplication. Then
fix Function::getSource() so we can diagnose instance pointers being
null.

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

... using value_or instead of the if-else statement.

Function parameters need to be checked before the function is called.

This broke a builder:
https://lab.llvm.org/buildbot/#builders/139/builds/29923

Assert that the previous call left the stack empty, as well as that
successful interpretations leave an empty stack.

Without this, clients are unable to rename often-used symbols in larger
projects.

Reviewed By: kadircet

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

Repeated call to Instruction::hasMetadata() and lookup in
getContext().pImpl->ValueMetadata are not needed when we always work on
the same instruction, avoid them.

This simple change leads to interesting and consistent speedups in
compile time, around -0.5% according to http://llvm-compile-time-tracker.com, see

        http://llvm-compile-time-tracker.com/compare.php?from=9708d88017d0c9adaea65a4f5a5b589b67f292e2&to=88482b9addd5917e9c5226847efeb5451c5f78c0&stat=instructions

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

Now includes the name of the graph and duplicate section.

Reviewed By: michaelrj

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

Reviewed By: michaelrj

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

Reviewed By: michaelrj

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

Reviewed By: cota

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

... instead of mapping them to the intermediate object file.
This matches ld64.

Reviewed By: #lld-macho, Roger

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

Include symbol sizes (present after {D135883}) as well as an example of
a dead-stripped symbol.

One of the first few instructions being probed has an opcode that's more
likely to change with work on X86 target, so just regexp-ing it.

Programmers may use procedure without BIND(C) attribute to interoperate
with C code. For numerical/logical scalar with VALUE attribute, pass the
argument by value so that the behavior is consistent with gfortran or
nvfortran. The argument with the OPTIONAL attribute cannot be passed by
value since the actual argument may be absent.

For the derived type, pass-by-value is not supported yet, so pass the
argument by reference for now.

Reviewed By: jeanPerier

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

Adjust the automatic fixit to avoid adding superfluous semicolon.

Test plan: ninja check-all

Differential revision: https://reviews.llvm.org/D136399

Now that Fortran warnings are tested, one test is failing unexpectedly on
aarch64 even though it should run only for x86.  Disabling it for now
with "XFAIL: *" to get build bot back up until the test's configuration
can be properly corrected.

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

Reviewed By: Peiming, aartbik

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

The foldMemRefCast method is defined in memref namespace; the
foldTensorCast method is defined in tensor namespace. This revision
deletes the dup code and use the unified methods.

Reviewed By: dcaballe

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

Add time profiler for various constexpr evaluation events
so that slow event could be visible on the visualized flame chart.

Reviewed By: aaron.ballman

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

This exposed a missing type conversion for codegen

Reviewed By: Peiming

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

Reviewed By: aartbik

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

A recent upgrade to test_errors.py enabled verification of
warning messages.  One test had warning messages that depend
on *not* being run in Windows, and it now fails.  Add an
!UNSUPPORTED: system-windows line to it.

Enum definitions are currently spread throughout the op definitions
file, making it difficult to reason about both where they are, and
where to add new ones when necessary. The attribute definitions are
in a similarish case, where while they have a dedicated .td file, there
definitions/declarations are generated in the main LLVMDialect source
files. This makes it difficult to reason about how to cleanly add new
attributes/enums.

This commit adds a dedicated LLVMEnums.td file for enum definitions,
cleans up the AttrDefs.td file, and adds a new LLVMAttrs.cpp/.h file to
home enum/attr definitions moving forward. This makes it much cleaner to
add new attributes/enums to the LLVM dialect.

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

This enables find/replace of nested components for location attributes.

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

This greatly simplifies composing enums in attribute/type printers,
which currently reimplement these functions as needed.

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

This reverts commit 1cf1b361.

Reviewed By: cferris

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

Reviewed By: aartbik

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

SubElementInterfaces forbids all mutable types and attributes from
implementing `replaceImmediateSubElements`. However, this prohibits
literal structs, which are immutable, from implementing that function.
This patch defers the decision on whether to support
`replaceImmediateSubElements` to the individual types/attributes.

Depends on D136505

Reviewed By: rriddle

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

This keeps the current parser, however, since the mnemonic `vec` is
overloaded for both of these types.

Depends on D136499

Reviewed By: rriddle

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