llvm.org GIT mirror llvm / 24fc8d3
Merging r243999: ------------------------------------------------------------------------ r243999 | tbrethou | 2015-08-04 20:51:17 -0700 (Tue, 04 Aug 2015) | 2 lines Rename all references to old mailing lists to new lists.llvm.org address. ------------------------------------------------------------------------ git-svn-id: https://llvm.org/svn/llvm-project/llvm/branches/release_37@244768 91177308-0d34-0410-b5e6-96231b3b80d8 Hans Wennborg 4 years ago
25 changed file(s) with 61 addition(s) and 61 deletion(s). Raw diff Collapse all Expand all
5757 PROJ_SRC_ROOT := $(LLVM_SRC_ROOT)
5858 PROJ_SRC_DIR := $(LLVM_SRC_ROOT)$(patsubst $(PROJ_OBJ_ROOT)%,%,$(PROJ_OBJ_DIR))
5959
60 # See: http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20150323/268067.html
60 # See: http://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon-20150323/268067.html
6161 ifeq ($(LLVM_SRC_ROOT), $(LLVM_OBJ_ROOT))
6262 $(error In-source builds are not allowed. Please configure from a separate build directory!)
6363 endif
172172 also expected to generate an i8 store as an i8 store, and not an instruction
173173 which writes to surrounding bytes. (If you are writing a backend for an
174174 architecture which cannot satisfy these restrictions and cares about
175 concurrency, please send an email to llvmdev.)
175 concurrency, please send an email to llvm-dev.)
176176
177177 Unordered
178178 ---------
2727 from the coding standards. In the case of ``libc++``, this is because the
2828 naming and other conventions are dictated by the C++ standard. If you think
2929 there is a specific good reason to deviate from the standards here, please bring
30 it up on the LLVMdev mailing list.
30 it up on the LLVM-dev mailing list.
3131
3232 There are some conventions that are not uniformly followed in the code base
3333 (e.g. the naming convention). This is because they are relatively new, and a
2929 This policy is aimed at frequent contributors to LLVM. People interested in
3030 contributing one-off patches can do so in an informal way by sending them to the
3131 `llvm-commits mailing list
32 cs.uiuc.edu/mailman/listinfo/llvm-commits>`_ and engaging another
32 llvm.org/mailman/listinfo/llvm-commits>`_ and engaging another
3333 developer to see it through the process.
3434
3535 Developer Policies
4646 -------------
4747
4848 Developers should stay informed by reading at least the "dev" mailing list for
49 the projects you are interested in, such as `llvmdev
50 `_ for LLVM, `cfe-dev
51 `_ for Clang, or `lldb-dev
52 `_ for LLDB. If you are
49 the projects you are interested in, such as `llvm-dev
50 `_ for LLVM, `cfe-dev
51 `_ for Clang, or `lldb-dev
52 `_ for LLDB. If you are
5353 doing anything more than just casual work on LLVM, it is suggested that you also
5454 subscribe to the "commits" mailing list for the subproject you're interested in,
5555 such as `llvm-commits
56 `_, `cfe-commits
57 `_, or `lldb-commits
58 cs.uiuc.edu/mailman/listinfo/lldb-commits>`_. Reading the
56 llvm.org/mailman/listinfo/llvm-commits>`_, `cfe-commits
57 `_, or `lldb-commits
58 `_. Reading the
5959 "commits" list and paying attention to changes being made by others is a good
6060 way to see what other people are interested in and watching the flow of the
6161 project as a whole.
6262
6363 We recommend that active developers register an email account with `LLVM
6464 Bugzilla `_ and preferably subscribe to the `llvm-bugs
65 cs.uiuc.edu/mailman/listinfo/llvmbugs>`_ email list to keep track
65 llvm.org/mailman/listinfo/llvm-bugs>`_ email list to keep track
6666 of bugs and enhancements occurring in LLVM. We really appreciate people who are
6767 proactive at catching incoming bugs in their components and dealing with them
6868 promptly.
364364
365365 #. You are granted *commit-after-approval* to all parts of LLVM. To get
366366 approval, submit a `patch`_ to `llvm-commits
367 cs.uiuc.edu/mailman/listinfo/llvm-commits>`_. When approved,
367 llvm.org/mailman/listinfo/llvm-commits>`_. When approved,
368368 you may commit it yourself.
369369
370370 #. You are allowed to commit patches without approval which you think are
393393 ---------------------
394394
395395 When a developer begins a major new project with the aim of contributing it back
396 to LLVM, they should inform the community with an email to the `llvmdev
397 `_ email list, to the extent
396 to LLVM, they should inform the community with an email to the `llvm-dev
397 `_ email list, to the extent
398398 possible. The reason for this is to:
399399
400400 #. keep the community informed about future changes to LLVM,
607607
608608 We have no plans to change the license of LLVM. If you have questions or
609609 comments about the license, please contact the `LLVM Developer's Mailing
610 List dev@cs.uiuc.edu>`_.
610 List -dev@lists.llvm.org>`_.
611611
612612 Patents
613613 -------
1414 LLVM? Is it a new fundamental capability that LLVM does not support at its
1515 current incarnation or can it be synthesized from already pre-existing LLVM
1616 elements? If you are not sure, ask on the `LLVM-dev
17 mail.cs.uiuc.edu/mailman/listinfo/llvmdev>`_ list. The reason is that
17 lists.llvm.org/mailman/listinfo/llvm-dev>`_ list. The reason is that
1818 extending LLVM will get involved as you need to update all the different passes
1919 that you intend to use with your extension, and there are ``many`` LLVM analyses
2020 and transformations, so it may be quite a bit of work.
173173
174174 If you run across a case that you feel deserves to be covered here, please send
175175 a patch to `llvm-commits
176 cs.uiuc.edu/mailman/listinfo/llvm-commits>`_ for review.
176 llvm.org/mailman/listinfo/llvm-commits>`_ for review.
177177
178 If you have questions on these items, please direct them to `llvmdev
179 `_. The more relevant
178 If you have questions on these items, please direct them to `llvm-dev
179 `_. The more relevant
180180 context you are able to give to your question, the more likely it is to be
181181 answered.
182182
149149
150150 Please let us know whether you like it and what could be improved! We're still
151151 working on setting up a bug tracker, but you can email klimek-at-google-dot-com
152 and chandlerc-at-gmail-dot-com and CC the llvmdev mailing list with questions
152 and chandlerc-at-gmail-dot-com and CC the llvm-dev mailing list with questions
153153 until then. We also could use help implementing improvements. This sadly is
154154 really painful and hard because the Phabricator codebase is in PHP and not as
155155 testable as you might like. However, we've put exactly what we're deploying up
253253 If you have any questions or need any help creating an LLVM project, the LLVM
254254 team would be more than happy to help. You can always post your questions to
255255 the `LLVM Developers Mailing List
256 cs.uiuc.edu/pipermail/llvmdev/>`_.
256 llvm.org/pipermail/llvm-dev/>`_.
2222 For more information about LLVM, including information about the latest
2323 release, please check out the `main LLVM web site `_. If you
2424 have questions or comments, the `LLVM Developer's Mailing List
25 cs.uiuc.edu/mailman/listinfo/llvmdev>`_ is a good place to send
25 llvm.org/mailman/listinfo/llvm-dev>`_ is a good place to send
2626 them.
2727
2828 Note that if you are reading this file from a Subversion checkout or the main
564564 local restrictions on the intrinsics mentioned in their respective
565565 documentation. The current implementation in LLVM does not check the
566566 key relocation invariant, but this is ongoing work on developing such
567 a verifier. Please ask on llvmdev if you're interested in
567 a verifier. Please ask on llvm-dev if you're interested in
568568 experimenting with the current version.
569569
570570 .. _statepoint-utilities:
695695 you should probably schedule this pass immediately before it. The exception
696696 would be if you need to preserve abstract frame information (e.g. for
697697 deoptimization or introspection) at safepoints. In that case, ask on the
698 llvmdev mailing list for suggestions.
698 llvm-dev mailing list for suggestions.
699699
700700
701701 Bugs and Enhancements
706706 `_
707707 for [Statepoint] in the summary field. When filing new bugs, please
708708 use this tag so that interested parties see the newly filed bug. As
709 with most LLVM features, design discussions take place on `llvmdev
710 `_, and patches
709 with most LLVM features, design discussions take place on `llvm-dev
710 `_, and patches
711711 should be sent to `llvm-commits
712 `_ for review.
713
712 `_ for review.
713
66
77 .. warning::
88 This document is extremely rough. If you find something lacking, please
9 fix it, file a documentation bug, or ask about it on llvmdev.
9 fix it, file a documentation bug, or ask about it on llvm-dev.
1010
1111 Introduction
1212 ============
66
77 .. warning::
88 This document is extremely rough. If you find something lacking, please
9 fix it, file a documentation bug, or ask about it on llvmdev.
9 fix it, file a documentation bug, or ask about it on llvm-dev.
1010
1111 Introduction
1212 ============
424424 If you can't find what you need in these docs, try consulting the mailing
425425 lists.
426426
427 `Developer's List (llvmdev)`__
427 `Developer's List (llvm-dev)`__
428428 This list is for people who want to be included in technical discussions of
429429 LLVM. People post to this list when they have questions about writing code
430430 for or using the LLVM tools. It is relatively low volume.
431431
432 .. __: http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
432 .. __: http://lists.llvm.org/mailman/listinfo/llvm-dev
433433
434434 `Commits Archive (llvm-commits)`__
435435 This list contains all commit messages that are made when LLVM developers
438438 stay on the bleeding edge of LLVM development. This list is very high
439439 volume.
440440
441 .. __: http://lists.cs.uiuc.edu/pipermail/llvm-commits/
442
443 `Bugs & Patches Archive (llvmbugs)`__
441 .. __: http://lists.llvm.org/pipermail/llvm-commits/
442
443 `Bugs & Patches Archive (llvm-bugs)`__
444444 This list gets emailed every time a bug is opened and closed. It is
445 higher volume than the LLVMdev list.
446
447 .. __: http://lists.cs.uiuc.edu/pipermail/llvmbugs/
445 higher volume than the LLVM-dev list.
446
447 .. __: http://lists.llvm.org/pipermail/llvm-bugs/
448448
449449 `Test Results Archive (llvm-testresults)`__
450450 A message is automatically sent to this list by every active nightly tester
451451 when it completes. As such, this list gets email several times each day,
452452 making it a high volume list.
453453
454 .. __: http://lists.cs.uiuc.edu/pipermail/llvm-testresults/
454 .. __: http://lists.llvm.org/pipermail/llvm-testresults/
455455
456456 `LLVM Announcements List (llvm-announce)`__
457457 This is a low volume list that provides important announcements regarding
458458 LLVM. It gets email about once a month.
459459
460 .. __: http://lists.cs.uiuc.edu/mailman/listinfo/llvm-announce
460 .. __: http://lists.llvm.org/mailman/listinfo/llvm-announce
461461
462462 IRC
463463 ---
8989 Have fun - try doing something crazy and unusual. Building a language
9090 like everyone else always has, is much less fun than trying something a
9191 little crazy or off the wall and seeing how it turns out. If you get
92 stuck or want to talk about it, feel free to email the `llvmdev mailing
93 list `_: it has lots
92 stuck or want to talk about it, feel free to email the `llvm-dev mailing
93 list `_: it has lots
9494 of people who are interested in languages and are often willing to help
9595 out.
9696
168168 IR does not itself guarantee safety. The LLVM IR allows unsafe pointer
169169 casts, use after free bugs, buffer over-runs, and a variety of other
170170 problems. Safety needs to be implemented as a layer on top of LLVM and,
171 conveniently, several groups have investigated this. Ask on the `llvmdev
172 mailing list `_ if
171 conveniently, several groups have investigated this. Ask on the `llvm-dev
172 mailing list `_ if
173173 you are interested in more details.
174174
175175 Language-Specific Optimizations
219219 In addition to simple library knowledge, it is possible to embed a
220220 variety of other language-specific information into the LLVM IR. If you
221221 have a specific need and run into a wall, please bring the topic up on
222 the llvmdev list. At the very worst, you can always treat LLVM as if it
222 the llvm-dev list. At the very worst, you can always treat LLVM as if it
223223 were a "dumb code generator" and implement the high-level optimizations
224224 you desire in your front-end, on the language-specific AST.
225225
9494 Have fun - try doing something crazy and unusual. Building a language
9595 like everyone else always has, is much less fun than trying something a
9696 little crazy or off the wall and seeing how it turns out. If you get
97 stuck or want to talk about it, feel free to email the `llvmdev mailing
98 list `_: it has lots
97 stuck or want to talk about it, feel free to email the `llvm-dev mailing
98 list `_: it has lots
9999 of people who are interested in languages and are often willing to help
100100 out.
101101
173173 IR does not itself guarantee safety. The LLVM IR allows unsafe pointer
174174 casts, use after free bugs, buffer over-runs, and a variety of other
175175 problems. Safety needs to be implemented as a layer on top of LLVM and,
176 conveniently, several groups have investigated this. Ask on the `llvmdev
177 mailing list `_ if
176 conveniently, several groups have investigated this. Ask on the `llvm-dev
177 mailing list `_ if
178178 you are interested in more details.
179179
180180 Language-Specific Optimizations
224224 In addition to simple library knowledge, it is possible to embed a
225225 variety of other language-specific information into the LLVM IR. If you
226226 have a specific need and run into a wall, please bring the topic up on
227 the llvmdev list. At the very worst, you can always treat LLVM as if it
227 the llvm-dev list. At the very worst, you can always treat LLVM as if it
228228 were a "dumb code generator" and implement the high-level optimizations
229229 you desire in your front-end, on the language-specific AST.
230230
9797 uint64_t LoadAddr,
9898 size_t Size) {
9999 // On OS X OS X __register_frame takes a single FDE as an argument.
100 // See http://lists.cs.uiuc.edu/pipermail/llvmdev/2013-April/061768.html
100 // See http://lists.llvm.org/pipermail/llvm-dev/2013-April/061768.html
101101 const char *P = (const char *)Addr;
102102 const char *End = P + Size;
103103 do {
565565 does not put the tables in-line in the text. This is more like the llvm
566566 default jump table implementation. This might be useful sometime. Several
567567 revisions of patches are on the mailing list, beginning at:
568 http://lists.cs.uiuc.edu/pipermail/llvmdev/2009-June/022763.html
568 http://lists.llvm.org/pipermail/llvm-dev/2009-June/022763.html
569569
570570 //===---------------------------------------------------------------------===//
571571
5656 // Some things to try that should be better:
5757 // * 'mov hi, $src; mov $dst, hi', with hi as either r10 or r11
5858 // * 'movs $dst, $src' if cpsr isn't live
59 // See: http://lists.cs.uiuc.edu/pipermail/llvmdev/2014-August/075998.html
59 // See: http://lists.llvm.org/pipermail/llvm-dev/2014-August/075998.html
6060
6161 // 'MOV lo, lo' is unpredictable on < v6, so use the stack to do it
6262 AddDefaultPred(BuildMI(MBB, I, DL, get(ARM::tPUSH)))
105105 //===---------------------------------------------------------------------===//
106106
107107 It would be nice to revert this patch:
108 http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20060213/031986.html
108 http://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon-20060213/031986.html
109109
110110 And teach the dag combiner enough to simplify the code expanded before
111111 legalize. It seems plausible that this knowledge would let it simplify other
657657 // gains over vector when the container becomes very large due to the
658658 // specific access patterns. For more information see the mailing list
659659 // discussion on this:
660 // http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20120116/135228.html
660 // http://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon-20120116/135228.html
661661 std::deque nodesToProcess;
662662
663663 bool Changed = false;
2222
2323
2424 Note: If you notice missing or incorrect syntax highlighting, please contact
25 bugs [at] cs.uiuc.edu>; if you wish to provide a patch to improve the
25 -bugs [at] lists.llvm.org>; if you wish to provide a patch to improve the
2626 functionality, it will be most appreciated. Thank you.
99
1010
1111 Note: If you notice missing or incorrect syntax highlighting, please contact
12 bugs [at] cs.uiuc.edu>; if you wish to provide a patch to improve the
12 -bugs [at] lists.llvm.org>; if you wish to provide a patch to improve the
1313 functionality, it will be most appreciated. Thank you.
77 this file to ~/.kde/share/apps/katepart/syntax (or better yet, symlink it).
88
99 Note: If you notice missing or incorrect syntax highlighting, please contact
10 bugs [at] cs.uiuc.edu>; if you wish to provide a patch to improve the
10 -bugs [at] lists.llvm.org>; if you wish to provide a patch to improve the
1111 functionality, it will be most appreciated. Thank you.
1919 * To GTestStreamToHelper in include/gtest/internal/gtest-internal.h,
2020 added the ability to stream with raw_os_ostream.
2121 * To refresh Haiku support in include/gtest/internal/gtest-port.h,
22 see http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20100621/102898.html
22 see http://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon-20100621/102898.html
88 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.
99
1010 Note: If you notice missing or incorrect syntax highlighting, please contact
11 bugs [at] cs.uiuc.edu>; if you wish to provide a patch to improve the
11 -bugs [at] lists.llvm.org>; if you wish to provide a patch to improve the
1212 functionality, it will be most appreciated. Thank you.
1313
1414 If you find yourself working with LLVM Makefiles often, but you don't get syntax