[acc] Support for Optional arguments in firstprivate recipes (#190079)
Add support for explicit of implicit firstprivates that are Fortran
Optional arguments.
[AMDGPU] Add amdgcn.av.global.(load|store).b128 intrinsics
The two new intrinsica llvm.amdgcn.global.load.b128 and
llvm.amdgcn.global.store.b128 have availability and visibility semantics as
described in #191246. Each of them takes a scope operand that is then translated
to target-specific cache policy bits. This allows the user to control how the
side-effects of these loads and stores are made visible to other threads.
This is patch was extracted from #172090.
Co-authored-by: macurtis-amd <macurtis at amd.com>
Assisted-by: Claude Opus 4.6
[GlobalISel] Add GIM_CheckMachineOperandType for matching metadata operands
Add a new match table opcode GIM_CheckMachineOperandType and a
corresponding MachineOperandTypeMatcher class to support matching
operands by their MachineOperand type. This enables GlobalISel pattern
matching for intrinsics that have metadata operands (MVT::Metadata),
which previously could not be matched in the generated selector.
This is patch was extracted from #172090.
Co-authored-by: macurtis-amd <macurtis at amd.com>
Assisted-by: Claude Opus 4.6
devel/stat(svn|cvs): run_depends on java
Java is needed to run this. So I think it makes sense to add openjdk
to the run_depends. Although when it compiled with openjdk8 it didn't
really matter what openjdk you used to run it with. Let's use JAVA_DEFAULT.
Statsvn even puts the %%JAVA%% var in files/statsvn.in so the script
wouldn't work with another JDK.
Piggyback this on the portrevision bump of my previous commit.
Approved-by: no maintainer
[analyzer][NFC] Document getVarRegion shortcomings (#191168)
... more precisely, that the analyzer currently uses `NonParamVarRegion`
instances to represent parameters of the entrypoint stack frame and
parameters that are captured by inner lambdas or blocks.
In my recent commit f40c234191802154d5b3fc3209908c3f2d6e1649 I added a
FIXME note to the method `MemRegionManager::getVarRegion`, but now, as I
tried to implement that I realized that the situation is more complex.
As I don't have time to fix this right now, I'm pushing this commit to
remove the inaccurate FIXME and replace it with more accurate TODO notes
that explain the current (problematic) behavior of the codebase.
[NFC] autogenerate disassembler tests with invalid MSR/MRS use (#185970)
This patch makes certain dissambler tests, which produce invalid MRS/MSR
intsructions autogenerated to make them easier to modify in the future
and to reduce diff size of #185709
