[all-commits] [llvm/llvm-project] 85da17: [flang] Enumeration Type: (PR 1/5) Foundation type...
Krzysztof Parzyszek via All-commits
all-commits at lists.llvm.org
Mon Jun 8 11:53:37 PDT 2026
Branch: refs/heads/users/kparzysz/resolve-declare-target
Home: https://github.com/llvm/llvm-project
Commit: 85da175778b7ebaeb7e5a4b8275060e5a17b62c6
https://github.com/llvm/llvm-project/commit/85da175778b7ebaeb7e5a4b8275060e5a17b62c6
Author: kwyatt-ext <kwyatt.external at hpe.com>
Date: 2026-06-08 (Mon, 08 Jun 2026)
Changed paths:
M flang/include/flang/Parser/dump-parse-tree.h
M flang/include/flang/Parser/parse-tree.h
M flang/include/flang/Semantics/symbol.h
M flang/include/flang/Semantics/tools.h
M flang/include/flang/Semantics/type.h
M flang/lib/Evaluate/type.cpp
M flang/lib/Lower/ConvertType.cpp
M flang/lib/Parser/Fortran-parsers.cpp
M flang/lib/Parser/program-parsers.cpp
M flang/lib/Parser/unparse.cpp
M flang/lib/Semantics/resolve-names.cpp
M flang/lib/Semantics/symbol.cpp
M flang/lib/Semantics/tools.cpp
M flang/lib/Semantics/type.cpp
A flang/test/Parser/enumeration-type.f90
Log Message:
-----------
[flang] Enumeration Type: (PR 1/5) Foundation types + Parser (#192651)
This PR creates the concept of an ENUMERATION TYPE from the Fortran 2023
Standard. It is implemented as a special case of a Derived Type
internally to the compiler. It adds the parse/unparse support. The
compiler will be able to recognize the syntax of an ENUMERATION TYPE and
report to users that the feature is not yet implemented.
It is the 1st of 5 stacked PRs.
AI Usage Disclosure: AI tools (Claude Opus 4.6) were used to assist with
implementation of this feature and test code generation. I have
reviewed, modified, and tested all AI-generated code.
---------
Co-authored-by: Kevin Wyatt <kwyatt at hpe.com>
Commit: 8472bc79bf157925c87c3acb7dbb4ac4ddb3070d
https://github.com/llvm/llvm-project/commit/8472bc79bf157925c87c3acb7dbb4ac4ddb3070d
Author: khaki3 <47756807+khaki3 at users.noreply.github.com>
Date: 2026-06-08 (Mon, 08 Jun 2026)
Changed paths:
M flang/lib/Optimizer/CodeGen/CodeGen.cpp
M flang/test/Fir/CUDA/cuda-code-gen.mlir
Log Message:
-----------
[flang][cuda] Don't allocate managed descriptors for OpenACC data-clause boxes (#201957)
Example:
```fortran
module m
real(8), allocatable :: u(:,:,:,:) ! device-resident allocatable
contains
subroutine core(uf, n)
integer :: n
real(8) :: uf(n,n,n,5)
!$acc kernels loop present(uf) ! descriptor built for uf
...
end subroutine
subroutine wrap(n)
call core(u, n)
end subroutine
end module
```
In this code, the descriptor for `present(uf)` is only used by `acc`
data-clause ops (the kernel gets the clause result, not the box), so it
never needs to be device-accessible. But `isDeviceAllocation()` is true,
so it's allocated via `_FortranACUFAllocDescriptor` in managed memory
and never freed — leaking it and leaving stale descriptors when the
address is reused.
Fix: allocate a descriptor in managed memory only when truly
device-accessible — used by a GPU kernel launch
(`isUsedByGPULaunchFunc`), or device-allocated and not consumed by an
`acc` data-clause op. Add `isUsedByOpenACCDataClause` and gate the
`isDeviceAllocation` branch with it.
Commit: 8e5cf611110162aa59a77cfda8d0864537dcc23f
https://github.com/llvm/llvm-project/commit/8e5cf611110162aa59a77cfda8d0864537dcc23f
Author: Deric C. <cheung.deric at gmail.com>
Date: 2026-06-08 (Mon, 08 Jun 2026)
Changed paths:
M llvm/lib/Target/DirectX/DXIL.td
M llvm/lib/Target/DirectX/DXILOpLowering.cpp
A llvm/test/CodeGen/DirectX/Sample.ll
A llvm/test/CodeGen/DirectX/SampleLevel.ll
Log Message:
-----------
[DirectX] Implement lowering of Sample and SampleLevel (#201477)
Fixes https://github.com/llvm/llvm-project/issues/192547 and
https://github.com/llvm/llvm-project/issues/192550
The Sample and SampleLevel implementations are combined in this single
PR because the code is extremely similar and the changes are small
thanks to the refactoring of prior implementations of sample lowerings.
Assisted-by: Claude Opus 4.6
Commit: e643d7e7a3008e3b97a6d9a1912cd19549b712f2
https://github.com/llvm/llvm-project/commit/e643d7e7a3008e3b97a6d9a1912cd19549b712f2
Author: Chi-Chun, Chen <chichun.chen at hpe.com>
Date: 2026-06-08 (Mon, 08 Jun 2026)
Changed paths:
M flang/lib/Lower/OpenMP/OpenMP.cpp
M flang/lib/Optimizer/OpenMP/LowerWorkdistribute.cpp
M flang/lib/Utils/OpenMP.cpp
M mlir/include/mlir/Dialect/OpenMP/OpenMPClauses.td
M mlir/include/mlir/Dialect/OpenMP/OpenMPOps.td
M mlir/lib/Dialect/OpenMP/IR/OpenMPDialect.cpp
M mlir/lib/Target/LLVMIR/Dialect/OpenMP/OpenMPToLLVMIRTranslation.cpp
M mlir/test/Dialect/OpenMP/invalid.mlir
M mlir/test/Dialect/OpenMP/ops.mlir
M mlir/test/Target/LLVMIR/openmp-todo.mlir
Log Message:
-----------
[mlir][OpenMP] Add iterator support to map/motion clause (#197047)
Extend omp.target_data, omp.target_enter_data, omp.target_exit_data,
and omp.target_update to support `!omp.iterated<Ty>`.
This is part of feature work for llvm#188061
Assisted with copilot
Commit: 6befeaa7b57bdf31f4b249a4533eebaa4ffa0b4a
https://github.com/llvm/llvm-project/commit/6befeaa7b57bdf31f4b249a4533eebaa4ffa0b4a
Author: Jonathan L'Work <113400649+Jonathan03ant at users.noreply.github.com>
Date: 2026-06-08 (Mon, 08 Jun 2026)
Changed paths:
M llvm/lib/Target/AMDGPU/AMDGPURegBankLegalizeRules.cpp
M llvm/test/CodeGen/AMDGPU/llvm.amdgcn.quadmask.ll
M llvm/test/CodeGen/AMDGPU/llvm.amdgcn.wqm.ll
Log Message:
-----------
[AMDGPU][GlobalIsel] RegBankLegalize rules for amdgcn_s_quadmask, amdgcn_s_wqm (#201898)
Commit: 8b45994309c19752dd369e86487461f93c00532b
https://github.com/llvm/llvm-project/commit/8b45994309c19752dd369e86487461f93c00532b
Author: Justin T. Gibbs <gibbs at scsiguy.com>
Date: 2026-06-08 (Mon, 08 Jun 2026)
Changed paths:
M compiler-rt/cmake/config-ix.cmake
M compiler-rt/lib/asan/CMakeLists.txt
Log Message:
-----------
[asan] Enable exceptions for asan_new_delete.cpp translation unit (#200719)
Groundwork for #196388.
Preparation for a follow-up change that lets the throwing operator new
wrappers in asan_new_delete.cpp throw std::bad_alloc on OOM. To support
that, asan_new_delete.cpp must be compiled with -fexceptions and must be
able to include <new> (i.e. without -nostdinc++). The rest of the ASan
runtime stays compiled with -fno-exceptions and -nostdinc++.
NOTE: Comments in CMakeLists.txt are written assuming the follow-on
changes to use exceptions land, thus avoiding the need to update
this file again.
Build-system changes:
* Define ASAN_CXX_CFLAGS as ASAN_CFLAGS minus -fno-exceptions and
-nostdinc++ plus -fexceptions. Define ASAN_DYNAMIC_CXX_CFLAGS likewise
relative to ASAN_DYNAMIC_CFLAGS. RTTI stays disabled; libstdc++ /
libc++abi supply the bad_alloc typeinfo.
* Static build: switch RTAsan_cxx (which already contains only
${ASAN_CXX_SOURCES} = asan_new_delete.cpp) from ASAN_CFLAGS to
ASAN_CXX_CFLAGS. RTAsan (the C slice) is unchanged.
* Dynamic build: split the previous single RTAsan_dynamic object library
into two — RTAsan_dynamic keeps ${ASAN_SOURCES} (no change in flags) and
a new RTAsan_dynamic_cxx carries ${ASAN_CXX_SOURCES} with
ASAN_DYNAMIC_CXX_CFLAGS. Both shared clang_rt.asan link rules pull in
RTAsan_dynamic_cxx alongside RTAsan_dynamic so the linked .so retains
the same set of object files; only the compile flags for
asan_new_delete.cpp change.
NFC at runtime — the asan_new_delete.cpp source as of this commit does
not yet use exceptions or include <new>, so the new flags are inert. The
follow-up commit makes use of them.
Assisted by: Claude Opus 4.7
Commit: e45c65ead95c36146449b230b3a68bb9098b88e6
https://github.com/llvm/llvm-project/commit/e45c65ead95c36146449b230b3a68bb9098b88e6
Author: Charles Zablit <c_zablit at apple.com>
Date: 2026-06-08 (Mon, 08 Jun 2026)
Changed paths:
M lldb/include/lldb/Host/common/NativeProcessProtocol.h
M lldb/source/Host/windows/ConnectionConPTYWindows.cpp
M lldb/source/Plugins/Process/Windows/Common/NativeProcessWindows.cpp
M lldb/source/Plugins/Process/Windows/Common/NativeProcessWindows.h
M lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationServerLLGS.cpp
M lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp
Log Message:
-----------
[lldb][Windows] add stdin support to lldb-server (#201638)
This patch uses `IOHandlerProcessSTDIOWindows` to add support for STDIN
forwarding in `lldb-server.exe`.
This is part 1/3 of a set of 3 patches, which together, fix 2 dap tests
on Windows when using `LLDB_USE_LLDB_SERVER=1`:
- https://github.com/llvm/llvm-project/pull/201884
- https://github.com/llvm/llvm-project/pull/201885
This requires https://github.com/llvm/llvm-project/pull/202353.
rdar://178725947
Commit: ce0b332657237ef05b92e5c669ae30f750b6100a
https://github.com/llvm/llvm-project/commit/ce0b332657237ef05b92e5c669ae30f750b6100a
Author: Keith Smiley <keithbsmiley at gmail.com>
Date: 2026-06-08 (Mon, 08 Jun 2026)
Changed paths:
M llvm/test/tools/llvm-objcopy/MachO/install-name-tool-output.test
Log Message:
-----------
[llvm-objcopy][test] Improve install-name-tool -o tests (NFC) (#201883)
Based on feedback from https://github.com/llvm/llvm-project/pull/189495
Commit: bccb07ef10b135bd02042f121427c140d874640b
https://github.com/llvm/llvm-project/commit/bccb07ef10b135bd02042f121427c140d874640b
Author: Teresa Johnson <tejohnson at google.com>
Date: 2026-06-08 (Mon, 08 Jun 2026)
Changed paths:
M llvm/lib/Transforms/IPO/MemProfContextDisambiguation.cpp
M llvm/test/ThinLTO/X86/remark-missing-info.ll
M llvm/test/Transforms/MemProfContextDisambiguation/remark-missing-info.ll
Log Message:
-----------
[MemProf] Improve post cloning remark (#201620)
This makes the remark when we don't have context size info more
consistent with the one when we do, and clarifies that the first
coldness tag is for the context.
Commit: 7fab0bcc9519e645e8a7c6ff0c1edfd8628b5764
https://github.com/llvm/llvm-project/commit/7fab0bcc9519e645e8a7c6ff0c1edfd8628b5764
Author: satyanarayana reddy janga <satyajanga at fb.com>
Date: 2026-06-08 (Mon, 08 Jun 2026)
Changed paths:
M lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemoteLog.cpp
M lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemoteLog.h
Log Message:
-----------
[lldb] Add a "plugin" log category to the gdb-remote channel (#202359)
Add a GDBRLog::Plugin category (enabled with `log enable gdb-remote
plugin`) for logging lldb-server plugin activity, such as the
accelerator plugins.
Commit: 3a4c2ec2b427ce48ae817bcf2e67a371bc2b2f7e
https://github.com/llvm/llvm-project/commit/3a4c2ec2b427ce48ae817bcf2e67a371bc2b2f7e
Author: Yexuan Xiao <bizwen at nykz.org>
Date: 2026-06-08 (Mon, 08 Jun 2026)
Changed paths:
M clang/bindings/python/clang/cindex.py
M clang/docs/ReleaseNotes.rst
M clang/include/clang-c/Index.h
A clang/test/Index/print-type-predefined-sugar.cpp
M clang/tools/libclang/CXType.cpp
Log Message:
-----------
[clang] Fix PredefinedSugarType reported as CXType_Unexposed (#202209)
Fix #192268.
Commit: b2e37b668bc4550bf8c72806402b116eb5d72e66
https://github.com/llvm/llvm-project/commit/b2e37b668bc4550bf8c72806402b116eb5d72e66
Author: Wooseok Lee <wolee at amd.com>
Date: 2026-06-08 (Mon, 08 Jun 2026)
Changed paths:
M llvm/lib/Target/AMDGPU/AMDGPUInstCombineIntrinsic.cpp
M llvm/test/Transforms/InstCombine/AMDGPU/fmed3.ll
Log Message:
-----------
[AMDGPU] Fix fmed3 constant-fold sign-of-zero miscompile (#201896)
[AMDGPU] Fix fmed3 constant-fold sign-of-zero miscompile
fmed3AMDGCN identifies the maximum of three operands via
APFloat::compare,
then returns maxnum of the remaining two as the median. APFloat::compare
treats +0 and -0 as equal (cmpEqual), so for inputs like fmed3(-0, -0,
+0)
Max3=+0 incorrectly compares equal to Src0=-0, causing the wrong arm to
fire and returning +0 instead of the correct median -0.
Hardware v_med3_f32 sorts with -0 < +0 uniformly across all generations,
so fmed3(-0, -0, +0) must return -0.
Fix by replacing APFloat::compare equality checks with
APFloat::bitwiseIsEqual,
which distinguishes +0 from -0 by bit pattern. This is strictly correct:
the only case where compare returns cmpEqual but bitwiseIsEqual returns
false
is the +0/-0 pair, which is exactly the misidentification being fixed.
All
three arms of the helper are covered.
Affected inputs (all returning wrong +0 before the fix):
fmed3(-0, -0, +0), fmed3(-0, +0, -0), fmed3(+0, -0, -0)
fmed3(N, -0, +0), fmed3(-0, N, +0), fmed3(-0, +0, N) where N < 0
Commit: bf820ee556d923013ebd15f409d38dd6ac9f877b
https://github.com/llvm/llvm-project/commit/bf820ee556d923013ebd15f409d38dd6ac9f877b
Author: Florian Hahn <flo at fhahn.com>
Date: 2026-06-08 (Mon, 08 Jun 2026)
Changed paths:
M llvm/lib/Transforms/Vectorize/LoopVectorize.cpp
M llvm/test/Transforms/LoopVectorize/VPlan/vplan-print-after-all.ll
Log Message:
-----------
[VPlan] Use RUN_VPLAN_PASS for more VPlan transforms. (#202399)
Convert additional VPlan transform invocations to use RUN_VPLAN_PASS:
replaceWideCanonicalIVWithWideIV, materializeAliasMaskCheckBlock,
narrowInterleaveGroups, tryToConvertVPInstructionsToVPRecipes and
optimizeInductionLiveOutUsers. This enables more accurate transform
printing as well as extra verification.
The transforms in executePlan after dissolveLoopRegions are left as-is,
as the verifier does not yet handle the intermediate dissolved states.
Commit: 17449ef9b7296da8a10d46410c62f16fde98bcd6
https://github.com/llvm/llvm-project/commit/17449ef9b7296da8a10d46410c62f16fde98bcd6
Author: Chi-Chun, Chen <chichun.chen at hpe.com>
Date: 2026-06-08 (Mon, 08 Jun 2026)
Changed paths:
M flang/lib/Lower/OpenMP/ClauseProcessor.cpp
M flang/lib/Lower/OpenMP/Utils.cpp
M flang/lib/Lower/OpenMP/Utils.h
Log Message:
-----------
[flang][OpenMP][NFC] Share declare mapper helpers for iterator modifier lowering (#197752)
Move mapper lookup and implicit default mapper creation into reusable
OpenMP lowering helpers so regular map lowering and iterator-generated
map entries (#197757) can use the same resolution path.
This prepares Flang iterator modifier lowering for map and motion
clauses
without changing the generated IR for existing non-iterator maps.
Commit: 3ab997597e8a5f2920efdad01cf8c29673826ba0
https://github.com/llvm/llvm-project/commit/3ab997597e8a5f2920efdad01cf8c29673826ba0
Author: Krzysztof Parzyszek <Krzysztof.Parzyszek at amd.com>
Date: 2026-06-08 (Mon, 08 Jun 2026)
Changed paths:
M flang/include/flang/Parser/dump-parse-tree.h
M flang/include/flang/Parser/parse-tree.h
M flang/include/flang/Semantics/symbol.h
M flang/include/flang/Semantics/tools.h
M flang/include/flang/Semantics/type.h
M flang/lib/Evaluate/type.cpp
M flang/lib/Lower/ConvertType.cpp
M flang/lib/Parser/Fortran-parsers.cpp
M flang/lib/Parser/program-parsers.cpp
M flang/lib/Parser/unparse.cpp
M flang/lib/Semantics/resolve-names.cpp
M flang/lib/Semantics/symbol.cpp
M flang/lib/Semantics/tools.cpp
M flang/lib/Semantics/type.cpp
R flang/test/Parser/enumeration-type.f90
Log Message:
-----------
Revert "[flang] Enumeration Type: (PR 1/5) Foundation types + Parser" (#202408)
Reverts llvm/llvm-project#192651
It seems to be causing linker errors. Verified locally that reverting
this commit helps.
```
/usr/bin/ld: tools/flang/lib/Evaluate/CMakeFiles/FortranEvaluate.dir/type.cpp.o: in function `Fortran::evaluate::DynamicType::GetAlignment(Fortran::evaluate::TargetCharacteristics const&) const':
type.cpp:(.text._ZNK7Fortran8evaluate11DynamicType12GetAlignmentERKNS0_21TargetCharacteristicsE+0x71): undefined reference to `Fortran::semantics::DerivedTypeSpec::GetScope() const'
/usr/bin/ld: type.cpp:(.text._ZNK7Fortran8evaluate11DynamicType12GetAlignmentERKNS0_21TargetCharacteristicsE+0x87): undefined reference to `Fortran::semantics::DerivedTypeSpec::GetScope() const'
/usr/bin/ld: tools/flang/lib/Evaluate/CMakeFiles/FortranEvaluate.dir/type.cpp.o: in function `Fortran::evaluate::DynamicType::MeasureSizeInBytes(Fortran::evaluate::FoldingContext&, bool, std::optional<long>) const':
type.cpp:(.text._ZNK7Fortran8evaluate11DynamicType18MeasureSizeInBytesERNS0_14FoldingContextEbSt8optionalIlE+0x1ed): undefined reference to `Fortran::semantics::DerivedTypeSpec::GetScope() const'
/usr/bin/ld: type.cpp:(.text._ZNK7Fortran8evaluate11DynamicType18MeasureSizeInBytesERNS0_14FoldingContextEbSt8optionalIlE+0x202): undefined reference to `Fortran::semantics::DerivedTypeSpec::GetScope() const'
/usr/bin/ld: type.cpp:(.text._ZNK7Fortran8evaluate11DynamicType18MeasureSizeInBytesERNS0_14FoldingContextEbSt8optionalIlE+0x218): undefined reference to `Fortran::semantics::DerivedTypeSpec::GetScope() const'
clang++: error: linker command failed with exit code 1 (use -v to see invocation)
```
Commit: 0e211af09118d978bdea4795974a0dd086e0337f
https://github.com/llvm/llvm-project/commit/0e211af09118d978bdea4795974a0dd086e0337f
Author: Krzysztof Parzyszek <Krzysztof.Parzyszek at amd.com>
Date: 2026-06-08 (Mon, 08 Jun 2026)
Changed paths:
M clang/bindings/python/clang/cindex.py
M clang/docs/ReleaseNotes.rst
M clang/include/clang-c/Index.h
A clang/test/Index/print-type-predefined-sugar.cpp
M clang/tools/libclang/CXType.cpp
M compiler-rt/cmake/config-ix.cmake
M compiler-rt/lib/asan/CMakeLists.txt
M flang/lib/Lower/OpenMP/ClauseProcessor.cpp
M flang/lib/Lower/OpenMP/OpenMP.cpp
M flang/lib/Lower/OpenMP/Utils.cpp
M flang/lib/Lower/OpenMP/Utils.h
M flang/lib/Optimizer/CodeGen/CodeGen.cpp
M flang/lib/Optimizer/OpenMP/LowerWorkdistribute.cpp
M flang/lib/Utils/OpenMP.cpp
M flang/test/Fir/CUDA/cuda-code-gen.mlir
M lldb/include/lldb/Host/common/NativeProcessProtocol.h
M lldb/source/Host/windows/ConnectionConPTYWindows.cpp
M lldb/source/Plugins/Process/Windows/Common/NativeProcessWindows.cpp
M lldb/source/Plugins/Process/Windows/Common/NativeProcessWindows.h
M lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationServerLLGS.cpp
M lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp
M lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemoteLog.cpp
M lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemoteLog.h
M llvm/lib/Target/AMDGPU/AMDGPUInstCombineIntrinsic.cpp
M llvm/lib/Target/AMDGPU/AMDGPURegBankLegalizeRules.cpp
M llvm/lib/Target/DirectX/DXIL.td
M llvm/lib/Target/DirectX/DXILOpLowering.cpp
M llvm/lib/Transforms/IPO/MemProfContextDisambiguation.cpp
M llvm/lib/Transforms/Vectorize/LoopVectorize.cpp
M llvm/test/CodeGen/AMDGPU/llvm.amdgcn.quadmask.ll
M llvm/test/CodeGen/AMDGPU/llvm.amdgcn.wqm.ll
A llvm/test/CodeGen/DirectX/Sample.ll
A llvm/test/CodeGen/DirectX/SampleLevel.ll
M llvm/test/ThinLTO/X86/remark-missing-info.ll
M llvm/test/Transforms/InstCombine/AMDGPU/fmed3.ll
M llvm/test/Transforms/LoopVectorize/VPlan/vplan-print-after-all.ll
M llvm/test/Transforms/MemProfContextDisambiguation/remark-missing-info.ll
M llvm/test/tools/llvm-objcopy/MachO/install-name-tool-output.test
M mlir/include/mlir/Dialect/OpenMP/OpenMPClauses.td
M mlir/include/mlir/Dialect/OpenMP/OpenMPOps.td
M mlir/lib/Dialect/OpenMP/IR/OpenMPDialect.cpp
M mlir/lib/Target/LLVMIR/Dialect/OpenMP/OpenMPToLLVMIRTranslation.cpp
M mlir/test/Dialect/OpenMP/invalid.mlir
M mlir/test/Dialect/OpenMP/ops.mlir
M mlir/test/Target/LLVMIR/openmp-todo.mlir
Log Message:
-----------
Merge branch 'main' into users/kparzysz/resolve-declare-target
Compare: https://github.com/llvm/llvm-project/compare/bcd8fdd49a1d...0e211af09118
To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications
More information about the All-commits
mailing list