Replace links to archived mailing lists by links to Discourse forums
This commit is contained in:
Danny Mösch
Aaron Ballman
parent
59dadd178b
commit
a749e3295d
|
|
@ -11,8 +11,8 @@ This repository is only intended to be checked out inside of a full LLVM+Clang
|
|||
tree, and in the 'tools/extra' subdirectory of the Clang checkout.
|
||||
|
||||
All discussion regarding Clang, Clang-based tools, and code in this repository
|
||||
should be held using the standard Clang mailing lists:
|
||||
http://lists.llvm.org/mailman/listinfo/cfe-dev
|
||||
should be held using the standard Clang forum:
|
||||
https://discourse.llvm.org/c/clang
|
||||
|
||||
Code review for this tree should take place on the standard Clang patch and
|
||||
commit lists:
|
||||
|
|
|
|||
|
|
@ -19,8 +19,8 @@ Clang Static Analyzer: http://clang-analyzer.llvm.org/
|
|||
Information on the LLVM project: http://llvm.org/
|
||||
|
||||
If you have questions or comments about Clang, a great place to discuss them is
|
||||
on the Clang development mailing list:
|
||||
http://lists.llvm.org/mailman/listinfo/cfe-dev
|
||||
on the Clang forums:
|
||||
https://discourse.llvm.org/c/clang/
|
||||
|
||||
If you find a bug in Clang, please file it in the LLVM bug tracker:
|
||||
http://llvm.org/bugs/
|
||||
|
|
|
|||
|
|
@ -32,9 +32,9 @@
|
|||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
Mailing Lists
|
||||
Mailing List & Forums
|
||||
<ul>
|
||||
<li><a href="http://lists.llvm.org/mailman/listinfo/cfe-dev">cfe-dev</a></li>
|
||||
<li><a href="https://discourse.llvm.org/c/clang">Clang Frontend Forums</a></li>
|
||||
<li><a href="http://lists.llvm.org/mailman/listinfo/cfe-commits">cfe-commits</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ if ( !-d $ROOT ) { mkdir( $ROOT, 0777 ); }
|
|||
my $LOGFILE = "$ROOT/log.txt";
|
||||
my $FORM_URL = 'index.cgi';
|
||||
my $MAILADDR = 'sabre@nondot.org';
|
||||
my $CONTACT_ADDRESS = 'Questions or comments? Email the <a href="http://lists.llvm.org/mailman/listinfo/llvm-dev">LLVM-dev mailing list</a>.';
|
||||
my $CONTACT_ADDRESS = 'Questions or comments? Discuss on the <a href="https://discourse.llvm.org">LLVM forum</a>.';
|
||||
my $LOGO_IMAGE_URL = 'cathead.png';
|
||||
my $TIMEOUTAMOUNT = 20;
|
||||
$ENV{'LD_LIBRARY_PATH'} = '/home/vadve/shared/localtools/fc1/lib/';
|
||||
|
|
|
|||
|
|
@ -33,8 +33,7 @@
|
|||
|
||||
<div class="submenu">
|
||||
<label>Communication</label>
|
||||
<a href="http://lists.llvm.org/mailman/listinfo/cfe-users">cfe-users List</a>
|
||||
<a href="http://lists.llvm.org/mailman/listinfo/cfe-dev">cfe-dev List</a>
|
||||
<a href="https://discourse.llvm.org/c/clang">Clang Forum</a>
|
||||
<a href="http://lists.llvm.org/mailman/listinfo/cfe-commits">cfe-commits List</a>
|
||||
<a href="https://github.com/llvm/llvm-project/issues">Bug Reports</a>
|
||||
<a href="http://planet.clang.org/">Planet Clang</a>
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@
|
|||
|
||||
<div class="submenu">
|
||||
<label>Quick Links</label>
|
||||
<a href="http://lists.llvm.org/mailman/listinfo/llvm-dev">llvm-dev</a>
|
||||
<a href="https://discourse.llvm.org">LLVM Forum</a>
|
||||
<a href="http://lists.llvm.org/mailman/listinfo/llvm-commits">llvm-commits</a>
|
||||
<a href="http://llvm.org/bugs/">Bug Reports</a>
|
||||
<a href="https://github.com/llvm/llvm-project/tree/main/compiler-rt/">Browse Sources</a>
|
||||
|
|
|
|||
|
|
@ -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
|
||||
|
||||
|
|
|
|||
|
|
@ -200,25 +200,24 @@ and `Getting started with LLVM <https://llvm.org/docs/GettingStarted.html>`__.
|
|||
|
||||
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 <https://llvm.org/docs/Phabricator.html>`_. Please add `libcxx-commits` as a subscriber.
|
||||
Also make sure you are subscribed to the `libcxx-commits mailing list <http://lists.llvm.org/mailman/listinfo/libcxx-commits>`_.
|
||||
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 <http://lists.llvm.org/mailman/listinfo/libcxx-dev>`_.
|
||||
Send discussions and questions to the `libcxx forum`_.
|
||||
|
||||
|
||||
Quick Links
|
||||
===========
|
||||
* `LLVM Homepage <https://llvm.org/>`_
|
||||
* `libc++abi Homepage <http://libcxxabi.llvm.org/>`_
|
||||
* `LLVM bug tracker <https://github.com/llvm/llvm-project/labels/libc++/>`_
|
||||
* `libcxx-commits Mailing List`_
|
||||
* `libcxx-dev Mailing List`_
|
||||
* `LLVM Bug Tracker <https://github.com/llvm/llvm-project/labels/libc++/>`_
|
||||
* `libcxx-commits Mailing List <http://lists.llvm.org/mailman/listinfo/libcxx-commits>`_
|
||||
* `libcxx Forum <https://discourse.llvm.org/c/runtimes/libcxx/>`_
|
||||
* `Browse libc++ Sources <https://github.com/llvm/llvm-project/tree/main/libcxx/>`_
|
||||
|
|
|
|||
|
|
@ -78,27 +78,25 @@ and `Getting started with LLVM <https://llvm.org/docs/GettingStarted.html>`__.
|
|||
|
||||
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 <https://llvm.org/docs/Phabricator.html>`_. 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 <http://lists.llvm.org/mailman/listinfo/cfe-commits>`_.
|
||||
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 <http://lists.llvm.org/mailman/listinfo/cfe-dev>`_.
|
||||
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 <https://llvm.org/>`_
|
||||
* `LLVM bug tracker <https://github.com/llvm/llvm-project/labels/libunwind/>`_
|
||||
* `cfe-commits Mailing List`_
|
||||
* `cfe-dev Mailing List`_
|
||||
* `LLVM Bug Tracker <https://github.com/llvm/llvm-project/labels/libunwind/>`_
|
||||
* `cfe-dev Mailing List <http://lists.llvm.org/mailman/listinfo/cfe-dev>`_
|
||||
* `cfe-commits Mailing List <http://lists.llvm.org/mailman/listinfo/cfe-commits>`_
|
||||
* `Runtimes Forum <https://discourse.llvm.org/tags/c/runtimes>`_
|
||||
* `Browse libunwind Sources <https://github.com/llvm/llvm-project/blob/main/libunwind/>`_
|
||||
|
|
|
|||
|
|
@ -102,10 +102,10 @@ Additionally it builds:
|
|||
|
||||
See the :doc:`LLDB Build Page <resources/build>` for build instructions.
|
||||
|
||||
Discussions about LLDB should go to the `lldb-dev
|
||||
<http://lists.llvm.org/mailman/listinfo/lldb-dev>`__ mailing list. Commit
|
||||
Discussions about LLDB should go to the `LLDB forum
|
||||
<https://discourse.llvm.org/c/subprojects/lldb>`__. Commit
|
||||
messages are automatically sent to the `lldb-commits
|
||||
<http://lists.llvm.org/mailman/listinfo/lldb-commits>`__ mailing list , and
|
||||
<http://lists.llvm.org/mailman/listinfo/lldb-commits>`__ mailing list, and
|
||||
this is also the preferred mailing list for patch submissions.
|
||||
|
||||
See the :doc:`Projects page <status/projects>` if you are looking for some
|
||||
|
|
|
|||
|
|
@ -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
|
||||
|
|
|
|||
|
|
@ -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
|
||||
<http://lists.llvm.org/mailman/listinfo/llvm-dev>`_ list. The reason is that
|
||||
elements? If you are not sure, ask on the `LLVM forums
|
||||
<https://discourse.llvm.org>`_. 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.
|
||||
|
|
|
|||
|
|
@ -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 <http://lists.llvm.org/mailman/listinfo/llvm-dev>`_: 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
|
||||
<https://discourse.llvm.org>`_: 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 <http://lists.llvm.org/mailman/listinfo/llvm-dev>`_ if
|
||||
you are interested in more details.
|
||||
conveniently, several groups have investigated this. Ask on the `LLVM
|
||||
forums <https://discourse.llvm.org>`_ if you are interested in more details.
|
||||
|
||||
Language-Specific Optimizations
|
||||
-------------------------------
|
||||
|
|
|
|||
Loading…
Reference in New Issue