llvm.org GIT mirror llvm / f93e288
Update Bugzilla URLs in docs git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@295432 91177308-0d34-0410-b5e6-96231b3b80d8 Ismail Donmez 2 years ago
5 changed file(s) with 6 addition(s) and 6 deletion(s). Raw diff Collapse all Expand all
6161 project as a whole.
6363 We recommend that active developers register an email account with `LLVM
64 Bugzilla ://llvm.org/bugs/>`_ and preferably subscribe to the `llvm-bugs
64 Bugzilla s://bugs.llvm.org/>`_ and preferably subscribe to the `llvm-bugs
6565 `_ 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
260260 * The changes should not cause performance or correctness regressions in code
261261 compiled by LLVM on all applicable targets.
263 * You are expected to address any `Bugzilla bugs ://llvm.org/bugs/>`_ that
263 * You are expected to address any `Bugzilla bugs s://bugs.llvm.org/>`_ that
264264 result from your change.
266266 We prefer for this to be handled before submission but understand that it isn't
1818 to find the problem more easily.
2020 Once you have a reduced test-case, go to `the LLVM Bug Tracking System
21 ://llvm.org/bugs/enter_bug.cgi>`_ and fill out the form with the
21 s://bugs.llvm.org/enter_bug.cgi>`_ and fill out the form with the
2222 necessary details (note that you don't need to pick a category, just use
2323 the "new-bugs" category if you're not sure). The bug description should
2424 contain the following information:
182182 **PR**
183183 Problem report. A bug filed on `the LLVM Bug Tracking System
184 ://llvm.org/bugs/enter_bug.cgi>`_.
184 s://bugs.llvm.org/enter_bug.cgi>`_.
186186 **PRE**
187187 Partial Redundancy Elimination
29032903 When the JIT is configured to compile lazily (using
29042904 ``ExecutionEngine::DisableLazyCompilation(false)``), there is currently a `race
2905 condition ://llvm.org/bugs/show_bug.cgi?id=5184>`_ in updating call sites
2905 condition s://bugs.llvm.org/show_bug.cgi?id=5184>`_ in updating call sites
29062906 after a function is lazily-jitted. It's still possible to use the lazy JIT in a
29072907 threaded program if you ensure that only one thread at a time can call any
29082908 particular lazy stub and that the JIT lock guards any IR access, but we suggest
831831 Currently known bugs and enhancements under consideration can be
832832 tracked by performing a `bugzilla search
833 ://llvm.org/bugs/buglist.cgi?cmdtype=runnamed&namedcmd=Statepoint%20Bugs&list_id=64342>`_
833 s://bugs.llvm.org/buglist.cgi?cmdtype=runnamed&namedcmd=Statepoint%20Bugs&list_id=64342>`_
834834 for [Statepoint] in the summary field. When filing new bugs, please
835835 use this tag so that interested parties see the newly filed bug. As
836836 with most LLVM features, design discussions take place on `llvm-dev