diff --git a/llvm/docs/DeveloperPolicy.rst b/llvm/docs/DeveloperPolicy.rst index 9ec6fb84636f..97e057234379 100644 --- a/llvm/docs/DeveloperPolicy.rst +++ b/llvm/docs/DeveloperPolicy.rst @@ -62,7 +62,7 @@ way to see what other people are interested in and watching the flow of the project as a whole. We recommend that active developers register an email account with `LLVM -Bugzilla `_ and preferably subscribe to the `llvm-bugs +Bugzilla `_ and preferably subscribe to the `llvm-bugs `_ email list to keep track of bugs and enhancements occurring in LLVM. We really appreciate people who are proactive at catching incoming bugs in their components and dealing with them @@ -261,7 +261,7 @@ the future that the change is responsible for. For example: * The changes should not cause performance or correctness regressions in code compiled by LLVM on all applicable targets. -* You are expected to address any `Bugzilla bugs `_ that +* You are expected to address any `Bugzilla bugs `_ that result from your change. We prefer for this to be handled before submission but understand that it isn't diff --git a/llvm/docs/HowToSubmitABug.rst b/llvm/docs/HowToSubmitABug.rst index 9f997d2757dd..25cb2c8c80d3 100644 --- a/llvm/docs/HowToSubmitABug.rst +++ b/llvm/docs/HowToSubmitABug.rst @@ -19,7 +19,7 @@ section to narrow down the bug so that the person who fixes it will be able to find the problem more easily. Once you have a reduced test-case, go to `the LLVM Bug Tracking System -`_ and fill out the form with the +`_ and fill out the form with the necessary details (note that you don't need to pick a category, just use the "new-bugs" category if you're not sure). The bug description should contain the following information: diff --git a/llvm/docs/Lexicon.rst b/llvm/docs/Lexicon.rst index de929bec1b0e..5d16091e27e5 100644 --- a/llvm/docs/Lexicon.rst +++ b/llvm/docs/Lexicon.rst @@ -182,7 +182,7 @@ P **PR** Problem report. A bug filed on `the LLVM Bug Tracking System - `_. + `_. **PRE** Partial Redundancy Elimination diff --git a/llvm/docs/ProgrammersManual.rst b/llvm/docs/ProgrammersManual.rst index 1c96046bf40a..1e2e8eb02481 100644 --- a/llvm/docs/ProgrammersManual.rst +++ b/llvm/docs/ProgrammersManual.rst @@ -2903,7 +2903,7 @@ Another way is to only call ``getPointerToFunction()`` from the When the JIT is configured to compile lazily (using ``ExecutionEngine::DisableLazyCompilation(false)``), there is currently a `race -condition `_ in updating call sites +condition `_ in updating call sites after a function is lazily-jitted. It's still possible to use the lazy JIT in a threaded program if you ensure that only one thread at a time can call any particular lazy stub and that the JIT lock guards any IR access, but we suggest diff --git a/llvm/docs/Statepoints.rst b/llvm/docs/Statepoints.rst index 29b1be37a893..7f2b20544812 100644 --- a/llvm/docs/Statepoints.rst +++ b/llvm/docs/Statepoints.rst @@ -831,7 +831,7 @@ Bugs and Enhancements Currently known bugs and enhancements under consideration can be tracked by performing a `bugzilla search -`_ +`_ for [Statepoint] in the summary field. When filing new bugs, please use this tag so that interested parties see the newly filed bug. As with most LLVM features, design discussions take place on `llvm-dev