diff --git a/Makefile.config.in b/Makefile.config.in index 3258714ac59..9df9834f4db 100644 --- a/Makefile.config.in +++ b/Makefile.config.in @@ -58,7 +58,7 @@ LLVM_OBJ_ROOT := $(call realpath, @abs_top_builddir@) PROJ_SRC_ROOT := $(LLVM_SRC_ROOT) PROJ_SRC_DIR := $(LLVM_SRC_ROOT)$(patsubst $(PROJ_OBJ_ROOT)%,%,$(PROJ_OBJ_DIR)) -# See: http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20150323/268067.html +# See: http://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon-20150323/268067.html ifeq ($(LLVM_SRC_ROOT), $(LLVM_OBJ_ROOT)) $(error In-source builds are not allowed. Please configure from a separate build directory!) endif diff --git a/docs/Atomics.rst b/docs/Atomics.rst index 6c8303b2830..9068df46b02 100644 --- a/docs/Atomics.rst +++ b/docs/Atomics.rst @@ -173,7 +173,7 @@ Notes for code generation also expected to generate an i8 store as an i8 store, and not an instruction which writes to surrounding bytes. (If you are writing a backend for an architecture which cannot satisfy these restrictions and cares about - concurrency, please send an email to llvmdev.) + concurrency, please send an email to llvm-dev.) Unordered --------- diff --git a/docs/CodingStandards.rst b/docs/CodingStandards.rst index 498d76b04d8..de4f73c546b 100644 --- a/docs/CodingStandards.rst +++ b/docs/CodingStandards.rst @@ -28,7 +28,7 @@ Note that some code bases (e.g. ``libc++``) have really good reasons to deviate from the coding standards. In the case of ``libc++``, this is because the naming and other conventions are dictated by the C++ standard. If you think there is a specific good reason to deviate from the standards here, please bring -it up on the LLVMdev mailing list. +it up on the LLVM-dev mailing list. There are some conventions that are not uniformly followed in the code base (e.g. the naming convention). This is because they are relatively new, and a diff --git a/docs/DeveloperPolicy.rst b/docs/DeveloperPolicy.rst index ebf91b8af5f..005a325684e 100644 --- a/docs/DeveloperPolicy.rst +++ b/docs/DeveloperPolicy.rst @@ -30,7 +30,7 @@ This policy is also designed to accomplish the following objectives: This policy is aimed at frequent contributors to LLVM. People interested in contributing one-off patches can do so in an informal way by sending them to the `llvm-commits mailing list -`_ and engaging another +`_ and engaging another developer to see it through the process. Developer Policies @@ -47,23 +47,23 @@ Stay Informed ------------- Developers should stay informed by reading at least the "dev" mailing list for -the projects you are interested in, such as `llvmdev -`_ for LLVM, `cfe-dev -`_ for Clang, or `lldb-dev -`_ for LLDB. If you are +the projects you are interested in, such as `llvm-dev +`_ for LLVM, `cfe-dev +`_ for Clang, or `lldb-dev +`_ for LLDB. If you are doing anything more than just casual work on LLVM, it is suggested that you also subscribe to the "commits" mailing list for the subproject you're interested in, such as `llvm-commits -`_, `cfe-commits -`_, or `lldb-commits -`_. Reading the +`_, `cfe-commits +`_, or `lldb-commits +`_. Reading the "commits" list and paying attention to changes being made by others is a good 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 -`_ email list to keep track +`_ 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 promptly. @@ -365,7 +365,7 @@ If you have recently been granted commit access, these policies apply: #. You are granted *commit-after-approval* to all parts of LLVM. To get approval, submit a `patch`_ to `llvm-commits - `_. When approved, + `_. When approved, you may commit it yourself. #. You are allowed to commit patches without approval which you think are @@ -394,8 +394,8 @@ Making a Major Change --------------------- When a developer begins a major new project with the aim of contributing it back -to LLVM, they should inform the community with an email to the `llvmdev -`_ email list, to the extent +to LLVM, they should inform the community with an email to the `llvm-dev +`_ email list, to the extent possible. The reason for this is to: #. keep the community informed about future changes to LLVM, @@ -613,7 +613,7 @@ LICENSE.txt files specifically indicate that they contain GPL code. We have no plans to change the license of LLVM. If you have questions or comments about the license, please contact the `LLVM Developer's Mailing -List `_. +List `_. Patents ------- diff --git a/docs/ExtendingLLVM.rst b/docs/ExtendingLLVM.rst index 56c48af1ff3..3fd54c8360e 100644 --- a/docs/ExtendingLLVM.rst +++ b/docs/ExtendingLLVM.rst @@ -15,7 +15,7 @@ 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 +`_ list. 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/docs/Frontend/PerformanceTips.rst b/docs/Frontend/PerformanceTips.rst index 22b3fe45984..8d0abcd1c17 100644 --- a/docs/Frontend/PerformanceTips.rst +++ b/docs/Frontend/PerformanceTips.rst @@ -174,10 +174,10 @@ Adding to this document If you run across a case that you feel deserves to be covered here, please send a patch to `llvm-commits -`_ for review. +`_ for review. -If you have questions on these items, please direct them to `llvmdev -`_. The more relevant +If you have questions on these items, please direct them to `llvm-dev +`_. The more relevant context you are able to give to your question, the more likely it is to be answered. diff --git a/docs/Phabricator.rst b/docs/Phabricator.rst index 69bf3bfd103..98fbb5154ce 100644 --- a/docs/Phabricator.rst +++ b/docs/Phabricator.rst @@ -150,7 +150,7 @@ Status Please let us know whether you like it and what could be improved! We're still working on setting up a bug tracker, but you can email klimek-at-google-dot-com -and chandlerc-at-gmail-dot-com and CC the llvmdev mailing list with questions +and chandlerc-at-gmail-dot-com and CC the llvm-dev mailing list with questions until then. We also could use help implementing improvements. This sadly is really painful and hard because the Phabricator codebase is in PHP and not as testable as you might like. However, we've put exactly what we're deploying up diff --git a/docs/Projects.rst b/docs/Projects.rst index 095b87a65a1..46956642536 100644 --- a/docs/Projects.rst +++ b/docs/Projects.rst @@ -254,4 +254,4 @@ Further Help If you have any questions or need any help creating an LLVM project, the LLVM team would be more than happy to help. You can always post your questions to the `LLVM Developers Mailing List -`_. +`_. diff --git a/docs/ReleaseNotes.rst b/docs/ReleaseNotes.rst index 17c5c069d5f..7f14c2cde16 100644 --- a/docs/ReleaseNotes.rst +++ b/docs/ReleaseNotes.rst @@ -23,7 +23,7 @@ from the `LLVM releases web site `_. For more information about LLVM, including information about the latest release, please check out the `main LLVM web site `_. If you have questions or comments, the `LLVM Developer's Mailing List -`_ is a good place to send +`_ is a good place to send them. Note that if you are reading this file from a Subversion checkout or the main diff --git a/docs/Statepoints.rst b/docs/Statepoints.rst index 2b01374a9ec..731706256f5 100644 --- a/docs/Statepoints.rst +++ b/docs/Statepoints.rst @@ -567,7 +567,7 @@ The existing IR Verifier pass has been extended to check most of the local restrictions on the intrinsics mentioned in their respective documentation. The current implementation in LLVM does not check the key relocation invariant, but this is ongoing work on developing such -a verifier. Please ask on llvmdev if you're interested in +a verifier. Please ask on llvm-dev if you're interested in experimenting with the current version. .. _statepoint-utilities: @@ -698,7 +698,7 @@ If you are scheduling the RewriteStatepointsForGC pass late in the pass order, you should probably schedule this pass immediately before it. The exception would be if you need to preserve abstract frame information (e.g. for deoptimization or introspection) at safepoints. In that case, ask on the -llvmdev mailing list for suggestions. +llvm-dev mailing list for suggestions. Supported Architectures @@ -715,8 +715,8 @@ 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 `llvmdev -`_, and patches +with most LLVM features, design discussions take place on `llvm-dev +`_, and patches should be sent to `llvm-commits -`_ for review. +`_ for review. diff --git a/docs/TableGen/LangIntro.rst b/docs/TableGen/LangIntro.rst index 4d4551e8a6e..a148634e3ed 100644 --- a/docs/TableGen/LangIntro.rst +++ b/docs/TableGen/LangIntro.rst @@ -7,7 +7,7 @@ TableGen Language Introduction .. warning:: This document is extremely rough. If you find something lacking, please - fix it, file a documentation bug, or ask about it on llvmdev. + fix it, file a documentation bug, or ask about it on llvm-dev. Introduction ============ diff --git a/docs/TableGen/LangRef.rst b/docs/TableGen/LangRef.rst index 134afedbb7b..27b2c8beaa6 100644 --- a/docs/TableGen/LangRef.rst +++ b/docs/TableGen/LangRef.rst @@ -7,7 +7,7 @@ TableGen Language Reference .. warning:: This document is extremely rough. If you find something lacking, please - fix it, file a documentation bug, or ask about it on llvmdev. + fix it, file a documentation bug, or ask about it on llvm-dev. Introduction ============ diff --git a/docs/index.rst b/docs/index.rst index 5c04a4e3fc9..fcdea03c65f 100644 --- a/docs/index.rst +++ b/docs/index.rst @@ -425,12 +425,12 @@ Mailing Lists If you can't find what you need in these docs, try consulting the mailing lists. -`Developer's List (llvmdev)`__ +`Developer's List (llvm-dev)`__ This list is for people who want to be included in technical discussions of LLVM. People post to this list when they have questions about writing code for or using the LLVM tools. It is relatively low volume. - .. __: http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev + .. __: http://lists.llvm.org/mailman/listinfo/llvm-dev `Commits Archive (llvm-commits)`__ This list contains all commit messages that are made when LLVM developers @@ -439,26 +439,26 @@ lists. stay on the bleeding edge of LLVM development. This list is very high volume. - .. __: http://lists.cs.uiuc.edu/pipermail/llvm-commits/ + .. __: http://lists.llvm.org/pipermail/llvm-commits/ -`Bugs & Patches Archive (llvmbugs)`__ +`Bugs & Patches Archive (llvm-bugs)`__ This list gets emailed every time a bug is opened and closed. It is - higher volume than the LLVMdev list. + higher volume than the LLVM-dev list. - .. __: http://lists.cs.uiuc.edu/pipermail/llvmbugs/ + .. __: http://lists.llvm.org/pipermail/llvm-bugs/ `Test Results Archive (llvm-testresults)`__ A message is automatically sent to this list by every active nightly tester when it completes. As such, this list gets email several times each day, making it a high volume list. - .. __: http://lists.cs.uiuc.edu/pipermail/llvm-testresults/ + .. __: http://lists.llvm.org/pipermail/llvm-testresults/ `LLVM Announcements List (llvm-announce)`__ This is a low volume list that provides important announcements regarding LLVM. It gets email about once a month. - .. __: http://lists.cs.uiuc.edu/mailman/listinfo/llvm-announce + .. __: http://lists.llvm.org/mailman/listinfo/llvm-announce IRC --- diff --git a/docs/tutorial/LangImpl9.rst b/docs/tutorial/LangImpl9.rst index 33987687dee..6c43d53f90f 100644 --- a/docs/tutorial/LangImpl9.rst +++ b/docs/tutorial/LangImpl9.rst @@ -90,8 +90,8 @@ 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 `llvmdev mailing -list `_: it has lots +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. @@ -169,8 +169,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 `llvmdev -mailing list `_ if +conveniently, several groups have investigated this. Ask on the `llvm-dev +mailing list `_ if you are interested in more details. Language-Specific Optimizations @@ -220,7 +220,7 @@ safe to optimize that into "return 0;" because C specifies what the In addition to simple library knowledge, it is possible to embed a variety of other language-specific information into the LLVM IR. If you have a specific need and run into a wall, please bring the topic up on -the llvmdev list. At the very worst, you can always treat LLVM as if it +the llvm-dev list. At the very worst, you can always treat LLVM as if it were a "dumb code generator" and implement the high-level optimizations you desire in your front-end, on the language-specific AST. diff --git a/docs/tutorial/OCamlLangImpl8.rst b/docs/tutorial/OCamlLangImpl8.rst index 6f694931ef8..0346fa9fed1 100644 --- a/docs/tutorial/OCamlLangImpl8.rst +++ b/docs/tutorial/OCamlLangImpl8.rst @@ -95,8 +95,8 @@ 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 `llvmdev mailing -list `_: it has lots +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. @@ -174,8 +174,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 `llvmdev -mailing list `_ if +conveniently, several groups have investigated this. Ask on the `llvm-dev +mailing list `_ if you are interested in more details. Language-Specific Optimizations @@ -225,7 +225,7 @@ safe to optimize that into "return 0;" because C specifies what the In addition to simple library knowledge, it is possible to embed a variety of other language-specific information into the LLVM IR. If you have a specific need and run into a wall, please bring the topic up on -the llvmdev list. At the very worst, you can always treat LLVM as if it +the llvm-dev list. At the very worst, you can always treat LLVM as if it were a "dumb code generator" and implement the high-level optimizations you desire in your front-end, on the language-specific AST. diff --git a/lib/ExecutionEngine/RuntimeDyld/RTDyldMemoryManager.cpp b/lib/ExecutionEngine/RuntimeDyld/RTDyldMemoryManager.cpp index 044eee43c9e..ecd99004bad 100644 --- a/lib/ExecutionEngine/RuntimeDyld/RTDyldMemoryManager.cpp +++ b/lib/ExecutionEngine/RuntimeDyld/RTDyldMemoryManager.cpp @@ -98,7 +98,7 @@ void RTDyldMemoryManager::registerEHFrames(uint8_t *Addr, uint64_t LoadAddr, size_t Size) { // On OS X OS X __register_frame takes a single FDE as an argument. - // See http://lists.cs.uiuc.edu/pipermail/llvmdev/2013-April/061768.html + // See http://lists.llvm.org/pipermail/llvm-dev/2013-April/061768.html const char *P = (const char *)Addr; const char *End = P + Size; do { diff --git a/lib/Target/ARM/README.txt b/lib/Target/ARM/README.txt index 57dc6cb88be..090a003424a 100644 --- a/lib/Target/ARM/README.txt +++ b/lib/Target/ARM/README.txt @@ -566,7 +566,7 @@ Robert Muth started working on an alternate jump table implementation that does not put the tables in-line in the text. This is more like the llvm default jump table implementation. This might be useful sometime. Several revisions of patches are on the mailing list, beginning at: -http://lists.cs.uiuc.edu/pipermail/llvmdev/2009-June/022763.html +http://lists.llvm.org/pipermail/llvm-dev/2009-June/022763.html //===---------------------------------------------------------------------===// diff --git a/lib/Target/ARM/Thumb1InstrInfo.cpp b/lib/Target/ARM/Thumb1InstrInfo.cpp index 028119c264b..216e776932b 100644 --- a/lib/Target/ARM/Thumb1InstrInfo.cpp +++ b/lib/Target/ARM/Thumb1InstrInfo.cpp @@ -57,7 +57,7 @@ void Thumb1InstrInfo::copyPhysReg(MachineBasicBlock &MBB, // Some things to try that should be better: // * 'mov hi, $src; mov $dst, hi', with hi as either r10 or r11 // * 'movs $dst, $src' if cpsr isn't live - // See: http://lists.cs.uiuc.edu/pipermail/llvmdev/2014-August/075998.html + // See: http://lists.llvm.org/pipermail/llvm-dev/2014-August/075998.html // 'MOV lo, lo' is unpredictable on < v6, so use the stack to do it AddDefaultPred(BuildMI(MBB, I, DL, get(ARM::tPUSH))) diff --git a/lib/Target/README.txt b/lib/Target/README.txt index 282d9234c1a..7e9888cc13e 100644 --- a/lib/Target/README.txt +++ b/lib/Target/README.txt @@ -106,7 +106,7 @@ for 1,2,4,8 bytes. //===---------------------------------------------------------------------===// It would be nice to revert this patch: -http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20060213/031986.html +http://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon-20060213/031986.html And teach the dag combiner enough to simplify the code expanded before legalize. It seems plausible that this knowledge would let it simplify other diff --git a/lib/Transforms/Scalar/EarlyCSE.cpp b/lib/Transforms/Scalar/EarlyCSE.cpp index d536a937dce..029b44c2ea8 100644 --- a/lib/Transforms/Scalar/EarlyCSE.cpp +++ b/lib/Transforms/Scalar/EarlyCSE.cpp @@ -658,7 +658,7 @@ bool EarlyCSE::run() { // gains over vector when the container becomes very large due to the // specific access patterns. For more information see the mailing list // discussion on this: - // http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20120116/135228.html + // http://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon-20120116/135228.html std::deque nodesToProcess; bool Changed = false; diff --git a/utils/emacs/README b/utils/emacs/README index e83eeae4b07..d0f2bfbbb3e 100644 --- a/utils/emacs/README +++ b/utils/emacs/README @@ -23,5 +23,5 @@ are: Note: If you notice missing or incorrect syntax highlighting, please contact -; if you wish to provide a patch to improve the +; if you wish to provide a patch to improve the functionality, it will be most appreciated. Thank you. diff --git a/utils/jedit/README b/utils/jedit/README index 6a6c8c76cc3..00db9ecb16a 100644 --- a/utils/jedit/README +++ b/utils/jedit/README @@ -10,5 +10,5 @@ These are syntax highlighting files for the jEdit editor. Included are: Note: If you notice missing or incorrect syntax highlighting, please contact -; if you wish to provide a patch to improve the +; if you wish to provide a patch to improve the functionality, it will be most appreciated. Thank you. diff --git a/utils/kate/README b/utils/kate/README index efe53b7e237..46657e5d676 100644 --- a/utils/kate/README +++ b/utils/kate/README @@ -8,5 +8,5 @@ These are syntax highlighting files for the Kate editor. Included are: this file to ~/.kde/share/apps/katepart/syntax (or better yet, symlink it). Note: If you notice missing or incorrect syntax highlighting, please contact -; if you wish to provide a patch to improve the +; if you wish to provide a patch to improve the functionality, it will be most appreciated. Thank you. diff --git a/utils/unittest/googletest/README.LLVM b/utils/unittest/googletest/README.LLVM index 16bfffd8d5e..5f7fffe26a4 100644 --- a/utils/unittest/googletest/README.LLVM +++ b/utils/unittest/googletest/README.LLVM @@ -20,4 +20,4 @@ Modified as follows: * To GTestStreamToHelper in include/gtest/internal/gtest-internal.h, added the ability to stream with raw_os_ostream. * To refresh Haiku support in include/gtest/internal/gtest-port.h, - see http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20100621/102898.html + see http://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon-20100621/102898.html diff --git a/utils/vim/README b/utils/vim/README index 1fe00992b0a..8aea87924eb 100644 --- a/utils/vim/README +++ b/utils/vim/README @@ -9,7 +9,7 @@ To install copy all subdirectories to your $HOME/.vim or if you prefer create symlinks to the files here. Do not copy the vimrc file here it is only meant as an inspiration and starting point for those working on llvm c++ code. Note: If you notice missing or incorrect syntax highlighting, please contact -; if you wish to provide a patch to improve the +; if you wish to provide a patch to improve the functionality, it will be most appreciated. Thank you. If you find yourself working with LLVM Makefiles often, but you don't get syntax