Communication - cfe-users List - cfe-dev List + Clang Forum cfe-commits List Bug Reports Planet Clang diff --git a/compiler-rt/www/menu.html.incl b/compiler-rt/www/menu.html.incl index 9f82739..e128cc713 100644 --- a/compiler-rt/www/menu.html.incl +++ b/compiler-rt/www/menu.html.incl @@ -10,7 +10,7 @@

Quick Links - llvm-dev + LLVM Forum llvm-commits Bug Reports Browse Sources diff --git a/flang/docs/GettingInvolved.md b/flang/docs/GettingInvolved.md index ae6f05f..efae97e 100644 --- a/flang/docs/GettingInvolved.md +++ b/flang/docs/GettingInvolved.md @@ -16,12 +16,11 @@ The Flang Project welcomes contributions of all kinds. Please feel free to join the mailing list or the slack channel for discussions related to development of Flang. To understand the status of various developments in Flang please join the respective call. -## Mailing Lists +## Forum and Mailing Lists -[Developer's List (flang-dev)](http://lists.llvm.org/mailman/listinfo/flang-dev) +[Forum](https://discourse.llvm.org/c/subprojects/flang) - This list is for people who want to be included in technical discussions related to Flang. People post to this list when they have questions about writing code - for or using the Flang tools. It is relatively low volume. + Flang forums are for technical discussions, questions about writing code for, or using Flang tools. [Commits Archive (flang-commits)](http://lists.llvm.org/pipermail/flang-commits) @@ -49,7 +48,7 @@ To understand the status of various developments in Flang please join the respec - Time: On Wednesdays 8:30 Pacific Time, on the weeks alternating with regular Flang Community Technical Biweekly Call. - Meeting minutes are available in this [Google Doc](https://docs.google.com/document/d/10T-S2J3GrahpG4Ooif93NSTz2zBW0MQc_RlwHi0-afY/edit?usp=sharing). If you can not access the Google Doc, please send an email to Alexis Perry-Holby at aperry@lanl.gov requesting to be added to the access list. -- Minutes from older meetings were sent to [flang-dev](http://lists.llvm.org/mailman/listinfo/flang-dev). Search for `Flang Biweekly Sync - Notes`. +- Minutes from older meetings were posted on the [Flang forum](https://discourse.llvm.org/c/subprojects/flang). Search for `Flang Biweekly Sync - Notes`. ### Flang Community Technical Biweekly Call diff --git a/libcxx/docs/index.rst b/libcxx/docs/index.rst index 92a716d..1ebbbec 100644 --- a/libcxx/docs/index.rst +++ b/libcxx/docs/index.rst @@ -200,25 +200,24 @@ and `Getting started with LLVM `__. If you think you've found a bug in libc++, please report it using the `LLVM bug tracker`_. If you're not sure, you -can post a message to the `libcxx-dev mailing list`_ or on IRC. +can ask for support on the `libcxx forum`_ or on IRC. **Patches** If you want to contribute a patch to libc++, the best place for that is `Phabricator `_. Please add `libcxx-commits` as a subscriber. -Also make sure you are subscribed to the `libcxx-commits mailing list `_. +Also make sure you are subscribed to the `libcxx-commits mailing list`_. **Discussion and Questions** -Send discussions and questions to the -`libcxx-dev mailing list `_. +Send discussions and questions to the `libcxx forum`_. Quick Links =========== * `LLVM Homepage `_ * `libc++abi Homepage `_ -* `LLVM bug tracker `_ -* `libcxx-commits Mailing List`_ -* `libcxx-dev Mailing List`_ +* `LLVM Bug Tracker `_ +* `libcxx-commits Mailing List `_ +* `libcxx Forum `_ * `Browse libc++ Sources `_ diff --git a/libunwind/docs/index.rst b/libunwind/docs/index.rst index 99ee86c..a831529 100644 --- a/libunwind/docs/index.rst +++ b/libunwind/docs/index.rst @@ -78,27 +78,25 @@ and `Getting started with LLVM `__. If you think you've found a bug in libunwind, please report it using the `LLVM bug tracker`_. If you're not sure, you -can post a message to the `cfe-dev mailing list`_ or on IRC. -Please include "libunwind" in your subject. +can ask for support on the `Runtimes forum`_ or on IRC. +Please use the tag "libunwind" for new threads. **Patches** If you want to contribute a patch to libunwind, the best place for that is `Phabricator `_. Please include [libunwind] in the subject and -add `cfe-commits` as a subscriber. Also make sure you are subscribed to the -`cfe-commits mailing list `_. +add `cfe-commits` as a subscriber. Also make sure you are subscribed to the `cfe-commits mailing list`_. **Discussion and Questions** -Send discussions and questions to the -`cfe-dev mailing list `_. -Please include [libunwind] in the subject. +Send discussions and questions to the `Runtimes forum`_. Please add the tag "libunwind" to your post. Quick Links =========== * `LLVM Homepage `_ -* `LLVM bug tracker `_ -* `cfe-commits Mailing List`_ -* `cfe-dev Mailing List`_ +* `LLVM Bug Tracker `_ +* `cfe-dev Mailing List `_ +* `cfe-commits Mailing List `_ +* `Runtimes Forum `_ * `Browse libunwind Sources `_ diff --git a/lldb/docs/index.rst b/lldb/docs/index.rst index 4a59559..0877310 100644 --- a/lldb/docs/index.rst +++ b/lldb/docs/index.rst @@ -102,10 +102,10 @@ Additionally it builds: See the :doc:`LLDB Build Page ` for build instructions. -Discussions about LLDB should go to the `lldb-dev -`__ mailing list. Commit +Discussions about LLDB should go to the `LLDB forum +`__. Commit messages are automatically sent to the `lldb-commits -`__ mailing list , and +`__ mailing list, and this is also the preferred mailing list for patch submissions. See the :doc:`Projects page ` if you are looking for some diff --git a/llvm/docs/Contributing.rst b/llvm/docs/Contributing.rst index 3707274..7eda81c 100644 --- a/llvm/docs/Contributing.rst +++ b/llvm/docs/Contributing.rst @@ -147,7 +147,7 @@ of LLVM's high-level design, as well as its internals: .. __: http://www.aosabook.org/en/llvm.html -.. _Developer's List (llvm-dev): http://lists.llvm.org/mailman/listinfo/llvm-dev +.. _Forum: https://discourse.llvm.org .. _irc.oftc.net: irc://irc.oftc.net/llvm .. _beginner: https://github.com/llvm/llvm-project/issues?q=is%3Aopen+is%3Aissue+label%3Abeginner .. _bug tracker: https://github.com/llvm/llvm-project/issues @@ -155,4 +155,3 @@ of LLVM's high-level design, as well as its internals: .. _git-clang-format: https://reviews.llvm.org/source/llvm-github/browse/main/clang/tools/clang-format/git-clang-format .. _LLVM's Phabricator: https://reviews.llvm.org/ .. _LLVM's Open Projects page: https://llvm.org/OpenProjects.html#what -.. _LLVM Developer's mailing list: http://lists.llvm.org/mailman/listinfo/llvm-dev diff --git a/llvm/docs/ExtendingLLVM.rst b/llvm/docs/ExtendingLLVM.rst index 1dd5578..1237299 100644 --- a/llvm/docs/ExtendingLLVM.rst +++ b/llvm/docs/ExtendingLLVM.rst @@ -14,8 +14,8 @@ function, or a whole new instruction. When you come to this realization, stop and think. Do you really need to extend LLVM? Is it a new fundamental capability that LLVM does not support at its current incarnation or can it be synthesized from already pre-existing LLVM -elements? If you are not sure, ask on the `LLVM-dev -`_ list. The reason is that +elements? If you are not sure, ask on the `LLVM forums +`_. The reason is that extending LLVM will get involved as you need to update all the different passes that you intend to use with your extension, and there are ``many`` LLVM analyses and transformations, so it may be quite a bit of work. diff --git a/llvm/docs/tutorial/MyFirstLanguageFrontend/LangImpl10.rst b/llvm/docs/tutorial/MyFirstLanguageFrontend/LangImpl10.rst index d575e0a..7b9105b 100644 --- a/llvm/docs/tutorial/MyFirstLanguageFrontend/LangImpl10.rst +++ b/llvm/docs/tutorial/MyFirstLanguageFrontend/LangImpl10.rst @@ -87,10 +87,9 @@ For example, try adding: Have fun - try doing something crazy and unusual. Building a language like everyone else always has, is much less fun than trying something a little crazy or off the wall and seeing how it turns out. If you get -stuck or want to talk about it, feel free to email the `llvm-dev mailing -list `_: it has lots -of people who are interested in languages and are often willing to help -out. +stuck or want to talk about it, please post on the `LLVM forums +`_: it has lots of people who are interested +in languages and are often willing to help out. Before we end this tutorial, I want to talk about some "tips and tricks" for generating LLVM IR. These are some of the more subtle things that @@ -166,9 +165,8 @@ It is certainly possible to implement a safe language in LLVM, but LLVM IR does not itself guarantee safety. The LLVM IR allows unsafe pointer casts, use after free bugs, buffer over-runs, and a variety of other problems. Safety needs to be implemented as a layer on top of LLVM and, -conveniently, several groups have investigated this. Ask on the `llvm-dev -mailing list `_ if -you are interested in more details. +conveniently, several groups have investigated this. Ask on the `LLVM +forums `_ if you are interested in more details. Language-Specific Optimizations ------------------------------- -- 2.7.4