Home
last modified time | relevance | path

Searched refs:issue (Results 1 – 25 of 377) sorted by relevance

12345678910>>...16

/llvm-project-15.0.7/clang/www/
H A Dmake_cxx_dr_status17 def __init__(self, section, issue, url, status, title): argument
19 section, issue, url, status, title
28 _, url, issue = issue_link.split('"', 2)
30 issue = int(issue.split('>', 1)[1].split('<', 1)[0])
32 return DR(section, issue, url, status, title)
48 key = lambda dr: dr.issue)
96 def availability(issue): argument
97 status = status_map.get(issue, 'unknown')
169 assert dr.issue not in status_map, "have status for not-ready dr %s" % dr.issue
172 avail, avail_style = availability(dr.issue)
[all …]
/llvm-project-15.0.7/.github/workflows/
H A Dllvm-bugs.yml31 issue_number: context.issue.number,
35 .then((issue) => {
37 author : issue.data.user.login,
38 issue : issue.data.number,
39 title : issue.data.title,
40 url : issue.data.html_url,
41 labels : issue.data.labels.map((label) => label.name),
42 assignee : issue.data.assignees.map((assignee) => assignee.login),
43 body : issue.data.body
49 subject: `[Bug ${issue.data.number}] ${issue.data.title}`,
[all …]
H A Dissue-release-workflow.yml27 …COMMENT_BODY: ${{ github.event.action == 'opened' && github.event.issue.body || github.event.comme…
36 …contains(github.event.action == 'opened' && github.event.issue.body || github.event.comment.body, …
60 --issue-number ${{ github.event.issue.number }} \
87 --issue-number ${{ github.event.issue.number }} \
H A Dissue-subscriber.yml27 issue-subscriber \
28 --issue-number '${{ github.event.issue.number }}' \
H A Dnew-issues.yml13 add-labels: 'new issue'
/llvm-project-15.0.7/llvm/utils/git/
H A Dgithub-automation.py30 self.issue = self.repo.get_issue(issue_number)
38 self.issue.create_comment(comment)
176 def issue(self) -> github.Issue.Issue: member in ReleaseWorkflow
189 issue = self.issue
190 milestone = issue.milestone
218 self.issue.create_comment(self.make_ignore_comment(message))
232 issue = self.issue
233 comment = issue.create_comment(message)
234 issue.add_to_labels(self.CHERRY_PICK_FAILED_LABEL)
240 return self.issue.create_comment(message)
[all …]
/llvm-project-15.0.7/llvm/docs/
H A DSecurity.rst16 …issue reporter and key experts) while an issue is being investigated. After an issue becomes publi…
18 .. _report-security-issue:
20 How to report a security issue?
23 To report a security issue in the LLVM Project, please `open a new issue`_ in the LLVM project page…
169 When a new issue is filed, a template is provided to help issue reporters provide all relevant info…
187 * A security issue reporter (not necessarily an LLVM contributor) reports an issue.
189 …scuss in which circumstances (if any) an issue is relevant to security, and determine if it is a s…
196 * The issue champion obtains a CVE entry from MITRE_.
207 What is considered a security issue?
230 .. _open a new issue: https://bugs.chromium.org/p/llvm/issues/entry
[all …]
H A DBugLifeCycle.rst56 unless the issue is being :ref:`closed<Closing>`.
81 * If the issue is with a particular revision of the C or C++ standard, please
88 * Add the ``good first issue`` label if you think this would be a good bug to
112 * If the issue has been resolved by a particular commit, close the issue with
116 messages and will automatically close the specified issue with a reference
119 * If the reported behavior is not a bug, it is appropriate to close the issue
123 * If the bug duplicates another issue, close it as a duplicate by adding the
124 ``duplicate`` label with a comment pointing to the issue it duplicates.
126 * If there is a sound reason for not fixing the issue (difficulty, ABI, open
146 open an issue asking to create an issue label and add the ``infrastructure``
[all …]
H A DGitHub.rst22 following commands on any issue that has been added to one of the "X.Y.Z Release"
32 the issue. If the commit(s) do apply cleanly, then a pull request will
H A DGitRepositoryPolicy.md5 cases please create an issue with the
25 To request a new repository, please create an issue with the
H A Dindex.rst90 Reporting a security issue
92 * :ref:`report-security-issue`
/llvm-project-15.0.7/llvm/test/DebugInfo/X86/
H A Dsymbolize-debug-fission-single.test2 # 1) clang++ -g -gsplit-dwarf=single splitdwarf-single-issue.cpp -O3 -o splitdwarf-single-issue.s -S
29 # CHECK-NEXT: {{.*}}splitdwarf-single-issue.cpp:7:3
31 # CHECK-NEXT: {{.*}}splitdwarf-single-issue.cpp:13:3
34 .file "splitdwarf-single-issue.cpp"
52 .file 1 "." "splitdwarf-single-issue.cpp"
53 .loc 1 11 0 # splitdwarf-single-issue.cpp:11:0
59 .loc 1 7 3 prologue_end # splitdwarf-single-issue.cpp:7:3
62 .loc 1 15 1 # splitdwarf-single-issue.cpp:15:1
164 .asciz "splitdwarf-single-issue.cpp" # string offset=124
/llvm-project-15.0.7/clang/test/Analysis/
H A Dcxx-member-initializer-const-field.cpp21 static auto issue() { in issue() function
35 static int issue() { in issue() function
50 static int issue(int y) { in issue() function
H A Dsolver-sym-simplification-ptr-bool.cl5 // This test case covers an issue found in the static analyzer
7 // architectures. This issue was originally discovered on a downstream,
/llvm-project-15.0.7/llvm/lib/Target/AArch64/
H A DAArch64SchedKryo.td15 // The issue width is set to five, matching the five issue queues for expanded
17 // but these do not actually take up an issue queue.
20 let IssueWidth = 5; // 5-wide issue for expanded uops
21 let MicroOpBufferSize = 128; // Out-of-order with temporary unified issue buffer
/llvm-project-15.0.7/llvm/test/CodeGen/ARM/
H A Dproc-resource-sched.ll15 ; Cortex-R52 model describes it as dual-issue with two integer ALUs
16 ; It should be able to issue the two additions in the same cycle.
H A Dtail-call-scheduling.ll5 ; Unfortunately, this test is sort of fragile... the original issue only
7 ; it anyway just to demonstrate the issue.
/llvm-project-15.0.7/clang/test/Analysis/scan-build/
H A Dhtml_output.test23 // The index should have a link to the report for the single issue.
29 // The report should describe the issue.
/llvm-project-15.0.7/clang/utils/analyzer/
H A DCmpRuns.py325 def add_common(self, issue: AnalysisDiagnostic):
326 self.present_in_both.append(issue)
328 def add_removed(self, issue: AnalysisDiagnostic):
329 self.present_only_in_old.append(issue)
331 def add_added(self, issue: AnalysisDiagnostic):
332 self.present_only_in_new.append(issue)
/llvm-project-15.0.7/flang/test/Lower/
H A Darray-character.f9085 call issue(c1, c2)
/llvm-project-15.0.7/clang/test/Parser/
H A Dobjc-init.m44 // expected-note@-3 {{insert an explicit cast to silence this issue}}
49 // expected-note@-3 {{insert an explicit cast to silence this issue}}
/llvm-project-15.0.7/lld/test/ELF/
H A Dppc64-error-toc-tail-call.s13 # A tail call to an external function without a nop should issue an error.
/llvm-project-15.0.7/bolt/test/X86/
H A Dissue26.s1 # This reproduces issue 26 from our github repo
/llvm-project-15.0.7/libcxx/cmake/caches/
H A DGeneric-asan.cmake2 # This is a temporary (hopefully) workaround for an ASan issue (see https://llvm.org/D119410).
/llvm-project-15.0.7/
H A DSECURITY.md4 [LLVM Security Group](https://llvm.org/docs/Security.html#how-to-report-a-security-issue)

12345678910>>...16