Skip to content

Conversation

@rootjalex
Copy link
Contributor

Noticed the link was dead when reading the docs. According to the wayback machine, it was a link to "Revisiting Out-of-SSA Translation for Correctness, Code Quality, and Efficiency" by Boissinot et al., so providing a more permanent link.

@github-actions
Copy link

github-actions bot commented Dec 5, 2025

Thank you for submitting a Pull Request (PR) to the LLVM Project!

This PR will be automatically labeled and the relevant teams will be notified.

If you wish to, you can add reviewers by using the "Reviewers" section on this page.

If this is not working for you, it is probably because you do not have write permissions for the repository. In which case you can instead tag reviewers by name in a comment by using @ followed by their GitHub username.

If you have received no comments on your PR for a week, you can request a review by "ping"ing the PR by adding a comment “Ping”. The common courtesy "ping" rate is once a week. Please remember that you are asking for valuable time from other developers.

If you have further questions, they may be answered by the LLVM GitHub User Guide.

You can also ask questions in a comment on this PR, on the LLVM Discord or on the forums.

@llvmbot llvmbot added the mlir label Dec 5, 2025
@rootjalex rootjalex changed the title Update broken link in MLIR LangRef.md [MLIR] Update broken link in LangRef.md Dec 5, 2025
@llvmbot
Copy link
Member

llvmbot commented Dec 5, 2025

@llvm/pr-subscribers-mlir

Author: Alexander Root (rootjalex)

Changes

Noticed the link was dead when reading the docs. According to the wayback machine, it was a link to "Revisiting Out-of-SSA Translation for Correctness, Code Quality, and Efficiency" by Boissinot et al., so providing a more permanent link.


Full diff: https://github.com/llvm/llvm-project/pull/170938.diff

1 Files Affected:

  • (modified) mlir/docs/LangRef.md (+1-1)
diff --git a/mlir/docs/LangRef.md b/mlir/docs/LangRef.md
index 10cfba908ee45..b1da4b9360592 100644
--- a/mlir/docs/LangRef.md
+++ b/mlir/docs/LangRef.md
@@ -424,7 +424,7 @@ func.func @simple(i64, i1) -> i64 {
 **Context:** The "block argument" representation eliminates a number of special
 cases from the IR compared to traditional "PHI nodes are operations" SSA IRs
 (like LLVM). For example, the
-[parallel copy semantics](http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.524.5461&rep=rep1&type=pdf)
+[parallel copy semantics](https://ieeexplore.ieee.org/document/4907656)
 of SSA is immediately apparent, and function arguments are no longer a special
 case: they become arguments to the entry block
 [[more rationale](Rationale/Rationale.md/#block-arguments-vs-phi-nodes)]. Blocks

@joker-eph joker-eph merged commit dda0486 into llvm:main Dec 6, 2025
9 of 12 checks passed
@github-actions
Copy link

github-actions bot commented Dec 6, 2025

@rootjalex Congratulations on having your first Pull Request (PR) merged into the LLVM Project!

Your changes will be combined with recent changes from other authors, then tested by our build bots. If there is a problem with a build, you may receive a report in an email or a comment on this PR.

Please check whether problems have been caused by your change specifically, as the builds can include changes from many authors. It is not uncommon for your change to be included in a build that fails due to someone else's changes, or infrastructure issues.

How to do this, and the rest of the post-merge process, is covered in detail here.

If your change does cause a problem, it may be reverted, or you can revert it yourself. This is a normal part of LLVM development. You can fix your changes and open a new PR to merge them again.

If you don't get any reports, no action is required from you. Your changes are working as expected, well done!

@github-actions
Copy link

github-actions bot commented Dec 6, 2025

⚠️ We detected that you are using a GitHub private e-mail address to contribute to the repo.
Please turn off Keep my email addresses private setting in your account.
See LLVM Developer Policy and LLVM Discourse for more information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants