| /llvm-project/clang/www/ |
| H A D | cxx_dr_status.html | 51 <td><a href="https://cplusplus.github.io/CWG/issues/1.html">1</a></td>
57 <td><a href="https://cplusplus.github.io/CWG/issues/2.html">2</a></td>
63 <td><a href="https://cplusplus.github.io/CWG/issues/3.html">3</a></td>
69 <td><a href="https://cplusplus.github.io/CWG/issues/4.html">4</a></td>
75 <td><a href="https://cplusplus.github.io/CWG/issues/5.html">5</a></td>
81 <td><a href="https://cplusplus.github.io/CWG/issues/6.html">6</a></td>
87 <td><a href="https://cplusplus.github.io/CWG/issues/7.html">7</a></td>
93 <td><a href="https://cplusplus.github.io/CWG/issues/8.html">8</a></td>
99 <td><a href="https://cplusplus.github.io/CWG/issues/9.html">9</a></td>
105 <td><a href="https://cplusplus.github.io/CWG/issues/1
[all...] |
| /llvm-project/llvm/docs/ |
| H A D | SecurityTransparencyReports.rst | 18 * We defined details on how to report security issues, see `this commit on
30 reports to be security issues:
32 * https://bugs.chromium.org/p/llvm/issues/detail?id=5
33 * https://bugs.chromium.org/p/llvm/issues/detail?id=11
35 Both issues were addressed with source changes: #5 in clangd/vscode-clangd, and
49 In this section we report on the issues the group received in 2022, or on issues
52 In 2022, the llvm security group received 15 issues that have been disclosed at
55 5 of these were judged to be security issues:
57 * https://bugs.chromium.org/p/llvm/issues/detail?id=17 reports a miscompile in
61 * https://bugs.chromium.org/p/llvm/issues/detail?id=19 reports a vulnerability
[all …]
|
| H A D | Security.rst | 7 1. Allow LLVM contributors and security researchers to disclose security-related issues affecting the LLVM project to members of the LLVM community.
8 2. Organize fixes, code reviews, and release management for said issues.
13 *Note*: these goals ensure timely action, provide disclosure timing when issues are reported, and respect vendors' / packagers' / users' constraints.
68 + Specializes in fixing compiler-based security related issues or often participates in their exploration and resolution.
80 + Represents an organization or company which ships products that include their own copy of LLVM. Due to their position in the organization, the nominee has a reasonable need to know about security issues and disclosure embargoes.
120 Every year, the LLVM Security Response Group must publish a transparency report. The intent of this report is to keep the community informed by summarizing the disclosures that have been made public in the last year. It shall contain a list of all public disclosures, as well as statistics on time to fix issues, length of embargo periods, and so on.
131 LLVM Security Response Group members will be subscribed to a private `Discussion Medium`_. It will be used for technical discussions of security issues, as well as process discussions about matters such as disclosure timelines and group membership. Members have access to all security issues.
139 * If the LLVM Security Response Group agrees, designated members may share issues with vendors of non-LLVM based products if their product suffers from the same issue. The non-LLVM vendor should be asked to respect the issue’s embargo date, and to not share the information beyond the need-to-know people within their organization.
140 * If the LLVM Security Response Group agrees, key experts can be brought in to help address particular issues
[all...] |
| H A D | SupportPolicy.rst | 68 avoid this by fixing all raised issues in a timely manner.
114 accidentally, reverting functionality and working on the issues offline
119 involved tasked to resolve the issues, still making sure the solution doesn't
153 After merge, there often is a period of transition, where teething issues on
180 There are multiple types of issues that might trigger a request for deprecation,
226 issues (depending on each case, as above), and if those are not fixed in time, a
234 of a modified version, with evidence that all of the issues were fixed and that
239 all of the issues that were listed as reasons for its original removal.
|
| H A D | FuzzingLLVM.rst | 28 __ https://bugs.chromium.org/p/oss-fuzz/issues/list?q=proj-llvm+clang-fuzzer
53 __ https://bugs.chromium.org/p/oss-fuzz/issues/list?q=proj-llvm+clang-format-fuzzer
70 __ https://bugs.chromium.org/p/oss-fuzz/issues/list?q=proj-llvm+llvm-dwarfdump-fuzzer
246 .. note:: You may run into issues if you build with BFD ld, which is the
247 default linker on many unix systems. These issues are being tracked
254 this did find issues, it didn't have a very good way to report problems in an
264 https://bugs.chromium.org/p/oss-fuzz/issues/list?q=Proj-llvm
|
| /llvm-project/.github/workflows/ |
| H A D | new-issues.yml | 1 name: Labeling new issues
3 issues:
10 automate-issues-labels:
12 issues: write
19 configuration-path: .github/new-issues-labeler.yml
|
| H A D | llvm-bugs.yml | 5 issues: read
8 issues:
36 github.rest.issues.get({
|
| H A D | issue-release-workflow.yml | 2 # to the release branch using comments on issues.
25 issues:
37 issues: write
|
| /llvm-project/lldb/test/API/functionalities/fork/concurrent_vfork/ |
| H A D | TestConcurrentVFork.py | 51 # https://github.com/llvm/llvm-project/issues/85084.
61 # https://github.com/llvm/llvm-project/issues/85084.
71 # https://github.com/llvm/llvm-project/issues/85084.
81 # https://github.com/llvm/llvm-project/issues/85084.
91 # https://github.com/llvm/llvm-project/issues/85084.
101 # https://github.com/llvm/llvm-project/issues/85084.
111 # https://github.com/llvm/llvm-project/issues/85084.
121 # https://github.com/llvm/llvm-project/issues/85084.
|
| /llvm-project/clang-tools-extra/test/clang-tidy/checkers/bugprone/ |
| H A D | suspicious-stringview-data-usage.cpp | 25 …call may not be null terminated, provide size information to the callee to prevent potential issues in invalid()
27 …call may not be null terminated, provide size information to the callee to prevent potential issues in invalid()
29 …call may not be null terminated, provide size information to the callee to prevent potential issues in invalid()
31 …call may not be null terminated, provide size information to the callee to prevent potential issues in invalid()
33 …call may not be null terminated, provide size information to the callee to prevent potential issues in invalid()
35 …call may not be null terminated, provide size information to the callee to prevent potential issues in invalid()
37 …call may not be null terminated, provide size information to the callee to prevent potential issues in invalid()
|
| /llvm-project/clang-tools-extra/docs/clang-tidy/checks/misc/ |
| H A D | header-include-cycle.rst | 27 in complex dependency cycles. Such cycles can cause issues with compilation
31 To address these issues, a check has been developed to detect cyclic
40 This specialized analysis helps identify and prevent issues related to header
44 identify and resolve these issues before they become more difficult and
53 cycles, and ignoring them helps to focus on potential issues within the
|
| /llvm-project/lldb/test/API/tools/lldb-server/vCont-threads/ |
| H A D | TestSignal.py | 60 oslist=["freebsd"], bugnumber="github.com/llvm/llvm-project/issues/56086"
91 oslist=["freebsd"], bugnumber="github.com/llvm/llvm-project/issues/56086"
111 oslist=["freebsd"], bugnumber="github.com/llvm/llvm-project/issues/56086"
131 oslist=["freebsd"], bugnumber="github.com/llvm/llvm-project/issues/56086"
148 oslist=["freebsd"], bugnumber="github.com/llvm/llvm-project/issues/56086"
164 oslist=["freebsd"], bugnumber="github.com/llvm/llvm-project/issues/56086"
185 oslist=["freebsd"], bugnumber="github.com/llvm/llvm-project/issues/56086"
205 oslist=["freebsd"], bugnumber="github.com/llvm/llvm-project/issues/56086"
|
| /llvm-project/clang-tools-extra/docs/clang-tidy/checks/bugprone/ |
| H A D | empty-catch.rst | 6 Detects and suggests addressing issues with empty catch statements.
24 lead to several issues, such as:
31 * *Security Issues*: Ignoring exceptions can lead to security issues, such as
44 To avoid these issues, developers should always handle exceptions properly.
122 bugs, security issues, poor code quality, and unreliable code. By handling
|
| H A D | multi-level-implicit-pointer-conversion.rst | 35 This results in an implicit pointer level conversion, which could cause issues
38 Using an explicit cast is a recommended solution to prevent issues caused by
43 caution can help catch potential issues early on in the development process,
|
| /llvm-project/llvm/test/CodeGen/X86/ |
| H A D | selectiondag-stackmap-legalize.ll | 138 ; https://github.com/llvm/llvm-project/issues/55613
141 ; - https://github.com/llvm/llvm-project/issues/26431
142 ; - https://github.com/llvm/llvm-project/issues/55957
145 ; - https://github.com/llvm/llvm-project/issues/55649
146 ; - https://github.com/llvm/llvm-project/issues/55957
|
| H A D | selectiondag-patchpoint-legalize.ll | 140 ; https://github.com/llvm/llvm-project/issues/55613
143 ; - https://github.com/llvm/llvm-project/issues/26431
144 ; - https://github.com/llvm/llvm-project/issues/55957
147 ; - https://github.com/llvm/llvm-project/issues/55649
148 ; - https://github.com/llvm/llvm-project/issues/55957
|
| /llvm-project/llvm/cmake/modules/ |
| H A D | CheckProblematicConfigurations.cmake | 13 # https://github.com/llvm/llvm-project/issues/54645
17 …d the /arch:AVX flag is known to cause issues with parts of LLVM.\nSee https://github.com/llvm/llv…
|
| /llvm-project/compiler-rt/lib/sanitizer_common/ |
| H A D | sanitizer_common_interceptors.inc | 1010 // https://github.com/google/sanitizers/issues/321.
1028 // https://github.com/google/sanitizers/issues/321.
1045 // https://github.com/google/sanitizers/issues/321.
1063 // https://github.com/google/sanitizers/issues/321.
1241 // https://github.com/google/sanitizers/issues/321.
1403 // https://github.com/google/sanitizers/issues/321.
1416 // https://github.com/google/sanitizers/issues/321.
1429 // https://github.com/google/sanitizers/issues/321.
1442 // https://github.com/google/sanitizers/issues/321.
1486 // https://github.com/google/sanitizers/issues/32
[all...] |
| /llvm-project/libcxx/test/std/utilities/function.objects/bind/func.bind/func.bind.bind/ |
| H A D | copy.pass.cpp | 16 // https://github.com/google/sanitizers/issues/1017
17 // https://github.com/google/sanitizers/issues/619
18 // https://github.com/google/sanitizers/issues/398
|
| /llvm-project/utils/bazel/llvm-project-overlay/lld/ |
| H A D | BUILD.bazel | 34 # See https://github.com/bazelbuild/bazel/issues/13803
64 # See https://github.com/bazelbuild/bazel/issues/13803
121 # See https://github.com/bazelbuild/bazel/issues/13803
205 # See https://github.com/bazelbuild/bazel/issues/13803
251 # See https://github.com/bazelbuild/bazel/issues/13803
|
| /llvm-project/libcxx/test/std/utilities/function.objects/func.wrap/func.wrap.func/ |
| H A D | robust_against_adl.pass.cpp | 16 // https://github.com/google/sanitizers/issues/1017
17 // https://github.com/google/sanitizers/issues/619
18 // https://github.com/google/sanitizers/issues/398
|
| /llvm-project/ |
| H A D | SECURITY.md | 1 # Reporting LLVM Security Issues
3 To report security issues in LLVM, please follow the steps outlined on the
|
| /llvm-project/llvm/docs/HistoricalNotes/ |
| H A D | 2000-12-06-MeetingSummary.txt | 6 ISSUES RESOLVED
48 UNRESOLVED ISSUES
59 of the LLVM when we design it? If so, several design issues should
|
| /llvm-project/clang/test/Misc/ |
| H A D | serialized-diags-no-issue.c | 7 // NOTE: it is important that this test case contains no issues. It tests
8 // that serialize diagnostics work in the absence of any issues.
|
| /llvm-project/libcxx/docs/ |
| H A D | Modules.rst | 75 `bug report <https://github.com/llvm/llvm-project/issues/61465>`__.
92 `bug report <https://github.com/llvm/llvm-project/issues/62943>`__.
257 # https://gitlab.kitware.com/cmake/cmake/-/issues/25916
258 # https://gitlab.kitware.com/cmake/cmake/-/issues/25539
284 <https://github.com/llvm/llvm-project/issues>`_. Please make sure the issue
|