Skip to content

Tags: rust-lang/llvm-project

Tags

rustc-1.86.0

Merge remote-tracking branch 'upstream/release/19.x' into rustc/19.1-…

…2024-12-03

rustc-1.85.1

Merge remote-tracking branch 'upstream/release/19.x' into rustc/19.1-…

…2024-12-03

rustc-1.85.0

Merge remote-tracking branch 'upstream/release/19.x' into rustc/19.1-…

…2024-12-03

rustc-1.84.0

Verified

This commit was signed with the committer’s verified signature.
dianqk dianqk
Revert "[ELF] Fix unnecessary inclusion of unreferenced provide symbols"

This reverts commit ebb326a.

rustc-1.83.0

Revert "[ELF] Fix unnecessary inclusion of unreferenced provide symbols"

This reverts commit ebb326a.

rustc-1.82.0

Revert "[ELF] Fix unnecessary inclusion of unreferenced provide symbols"

This reverts commit ebb326a.

rustc-1.81.0

[Mem2Reg] Always allow single-store optimization for dominating stores

In llvm#97711 the single-store optimization was disabled for the case
where the value is potentially poison, as this may produce incorrect
results for loads of uninitialized memory.

However, this resulted in compile-time regressions. Address these
by still allowing the single-store optimization to occur in cases
where the store dominates the load, as we know that such a load
will always read initialized memory.

(cherry picked from commit daaea12)

rustc-1.80.1

[Mem2Reg] Always allow single-store optimization for dominating stores

In llvm#97711 the single-store optimization was disabled for the case
where the value is potentially poison, as this may produce incorrect
results for loads of uninitialized memory.

However, this resulted in compile-time regressions. Address these
by still allowing the single-store optimization to occur in cases
where the store dominates the load, as we know that such a load
will always read initialized memory.

(cherry picked from commit daaea12)

rustc-1.80.0

[Mem2Reg] Always allow single-store optimization for dominating stores

In llvm#97711 the single-store optimization was disabled for the case
where the value is potentially poison, as this may produce incorrect
results for loads of uninitialized memory.

However, this resulted in compile-time regressions. Address these
by still allowing the single-store optimization to occur in cases
where the store dominates the load, as we know that such a load
will always read initialized memory.

(cherry picked from commit daaea12)

rustc-1.79.0

Merge remote-tracking branch 'upstream/release/18.x' into rustc/18.1-…

…2024-05-19