[SCEV] Remove unreachable visitMulExpr in SCEVCastSinkingRewriter (NFC) (#219279)
SCEVCastSinkingRewriter::visit() returns S unchanged unless S->getType()
is a pointer type. So visitMulExpr can never be entered.
Delete stale TPGs before creating/updating on tag changes
An ALUA toggle can move a target's TPG tag onto one that still holds the
old TPG's network portal, so a new tag's portal mkdir raced the old tag's
teardown. Delete first.
[mlir][OpenACC] Lower constant sized loop clauses (#219043)
Add support for sized loop clauses (`acc.loop
vector(n)/worker(n)/gang(num:n)`) in kernels constructs. Collect
constant sizes from kernels loops before conversion and add them to the
launch arguments. Treat the parallelism levels associated with sized
clauses as regular levels when assigning par_dims to loops. Non-constant
sizes remain NYI.
net/opentofu111: import opentofu111-1.11.14
OpenTofu is an OSS tool for building, changing, and versioning
infrastructure safely and efficiently. OpenTofu can manage existing and
popular service providers as well as custom in-house solutions.
The key features of OpenTofu are:
* Infrastructure as Code: Infrastructure is described using a
high-level configuration syntax. This allows a blueprint of your
datacenter to be versioned and treated as you would any other code.
Additionally, infrastructure can be shared and re-used.
* Execution Plans: OpenTofu has a "planning" step where it generates
an execution plan. The execution plan shows what OpenTofu will do
when you call apply. This lets you avoid any surprises when
OpenTofu manipulates infrastructure.
* Resource Graph: OpenTofu builds a graph of all your resources, and
parallelizes the creation and modification of any non-dependent
resources. Because of this, OpenTofu builds infrastructure as
[13 lines not shown]
net/opentofu110: import opentofu110-1.10.10
OpenTofu is an OSS tool for building, changing, and versioning
infrastructure safely and efficiently. OpenTofu can manage existing and
popular service providers as well as custom in-house solutions.
The key features of OpenTofu are:
* Infrastructure as Code: Infrastructure is described using a
high-level configuration syntax. This allows a blueprint of your
datacenter to be versioned and treated as you would any other code.
Additionally, infrastructure can be shared and re-used.
* Execution Plans: OpenTofu has a "planning" step where it generates
an execution plan. The execution plan shows what OpenTofu will do
when you call apply. This lets you avoid any surprises when
OpenTofu manipulates infrastructure.
* Resource Graph: OpenTofu builds a graph of all your resources, and
parallelizes the creation and modification of any non-dependent
resources. Because of this, OpenTofu builds infrastructure as
[13 lines not shown]
[MLIR][XeGPU][NFC] Fix WG integration tests for strict property assembly format (#219256)
b73a8b8d8c17 ("[MLIR][XeGPU] Enable strict property assembly format",
#217281) made inherent attributes stored as properties unparseable from
the trailing attr-dict, but two XeGPU workgroup integration tests still
write `layout` that way, so they fail to parse.
Move the affected `layout`/`layout_a`/`layout_b`/`layout_cd` operands
into the prop-dict position, `{...}` -> `<{...}>`, for
xegpu.load_matrix, store_matrix, load_nd, store_nd and dpas.
These tests only run when the Level Zero or SYCL runner is enabled
(MLIR_ENABLE_LEVELZERO_RUNNER / MLIR_ENABLE_SYCL_RUNNER), which is why
the breakage was not caught by the default CI configuration.
Co-authored-by: Claude Opus 5 (1M context) <noreply at anthropic.com>
net/opentofu16: import opentofu16-1.6.3
OpenTofu is an OSS tool for building, changing, and versioning
infrastructure safely and efficiently. OpenTofu can manage existing and
popular service providers as well as custom in-house solutions.
The key features of OpenTofu are:
* Infrastructure as Code: Infrastructure is described using a
high-level configuration syntax. This allows a blueprint of your
datacenter to be versioned and treated as you would any other code.
Additionally, infrastructure can be shared and re-used.
* Execution Plans: OpenTofu has a "planning" step where it generates
an execution plan. The execution plan shows what OpenTofu will do
when you call apply. This lets you avoid any surprises when
OpenTofu manipulates infrastructure.
* Resource Graph: OpenTofu builds a graph of all your resources, and
parallelizes the creation and modification of any non-dependent
resources. Because of this, OpenTofu builds infrastructure as
[13 lines not shown]
net: Remove opentofu
Several opentofu versions will be imported with version suffixes in order to
permit a full migration from Terraform.
Discussed on tech-pkg@ and no negative feedbacks
<https://mail-index.NetBSD.org/tech-pkg/2026/03/04/msg032042.html>
(it took a bit more than a week to import them though, sorry!)
opentofu: Remove, it will be imported as opentofu*
opentofu will be reimported as opentofu16, opentofu110 and opentofu111
in order to permit a complete Terraform to OpenTofu migration in
pkgsrc.
Discussed on tech-pkg@ and no negative feedbacks
<https://mail-index.NetBSD.org/tech-pkg/2026/03/04/msg032042.html>
(it took a bit more than a week to import them though, sorry!)
net/terraform15: import terraform15-1.5.7
Terraform is a tool for building, changing, and versioning
infrastructure safely and efficiently. Terraform can manage existing
and popular service providers as well as custom in-house solutions.
The key features of Terraform are:
- Infrastructure as Code: Infrastructure is described using a
high-level configuration syntax. This allows a blueprint of your
datacenter to be versioned and treated as you would any other
code. Additionally, infrastructure can be shared and re-used.
- Execution Plans: Terraform has a "planning" step where it generates
an execution plan. The execution plan shows what Terraform will do
when you call apply. This lets you avoid any surprises when
Terraform manipulates infrastructure.
- Resource Graph: Terraform builds a graph of all your resources, and
parallelizes the creation and modification of any non-dependent
resources. Because of this, Terraform builds infrastructure as
efficiently as possible, and operators get insight into dependencies
[12 lines not shown]
