Home
last modified time | relevance | path

Searched full:issue (Results 1 – 25 of 1402) sorted by relevance

12345678910>>...57

/llvm-project/clang/test/Misc/
H A Dserialized-diags-single-issue.c10 // NOTE: it is important that this test case only contain a single issue. This test case checks
13 …erialized-diags-single-issue.c:3:12: warning: variable 'voodoo' is uninitialized when used here [-…
14 // CHECK: Range: {{.*}}serialized-diags-single-issue.c:3:12 {{.*}}serialized-diags-single-issue.c:3…
15 // CHECK: +-{{.*}}serialized-diags-single-issue.c:2:13: note: initialize the variable 'voodoo' to s…
16 // CHECK: +-Range: {{.*}}serialized-diags-single-issue.c:2:13 {{.*}}serialized-diags-single-issue.c…
17 // CHECK: +-FIXIT: ({{.*}}serialized-diags-single-issue.c:2:13 - {{.*}}serialized-diags-single-issu…
24 // CHECK-MULT: {{.*}}serialized-diags-single-issue.c:3:12: warning: variable 'voodoo' is uninitiali…
25 // CHECK-MULT: Range: {{.*}}serialized-diags-single-issue.c:3:12 {{.*}}serialized-diags-single-issu…
26 // CHECK-MULT: +-{{.*}}serialized-diags-single-issue.c:2:13: note: initialize the variable 'voodoo'…
27 … CHECK-MULT: +-Range: {{.*}}serialized-diags-single-issue.c:2:13 {{.*}}serialized-diags-single-iss…
[all …]
H A Dserialized-diags.m20 …-diags.m:8:4: error: use of undeclared identifier '_self'; did you mean 'self'? [] [Semantic Issue]
24 // CHECK: +-(null):0:0: note: 'self' is an implicit parameter [] [Semantic Issue]
26 …: warning: class 'Foo' defined without specifying a base class [-Wobjc-root-class] [Semantic Issue]
28 …{{.*[/\\]}}serialized-diags.m:1:15: note: add a super class to fix this problem [] [Semantic Issue]
/llvm-project/.github/workflows/
H A Dllvm-bugs.yml37 issue_number: context.issue.number,
41 .then((issue) => {
43 author : issue.data.user.login,
44 issue : issue.data.number,
45 title : issue.data.title,
46 url : issue.data.html_url,
47 labels : issue.data.labels.map((label) => label.name),
48 assignee : issue.data.assignees.map((assignee) => assignee.login),
49 body : issue.data.body
55 subject: `[Bug ${issue.data.number}] ${issue.data.title}`,
[all …]
H A Dissue-release-workflow.yml15 name: Issue Release Workflow
30 …COMMENT_BODY: ${{ github.event.action == 'opened' && github.event.issue.body || github.event.comme…
42 …contains(github.event.action == 'opened' && github.event.issue.body || github.event.comment.body, …
67 --issue-number ${{ github.event.issue.number }} \
68 …--requested-by ${{ (github.event.action == 'opened' && github.event.issue.user.login) || github.ev…
H A Dissue-subscriber.yml1 name: Issue Subscriber
35 issue-subscriber \
36 --issue-number '${{ github.event.issue.number }}' \
/llvm-project/clang/www/
H A Dmake_cxx_dr_status13 def __init__(self, section, issue, url, status, title): argument
14 self.section, self.issue, self.url, self.status, self.title = \
15 section, issue, url, status, title
17 return '%s (%s): %s' % (self.issue, self.status, self.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)
59 print('Fetching issue list from {}'.format(issue_list_url))
63 print('Opening issue lis
143 availability(issue) global() argument
[all...]
/llvm-project/llvm/utils/git/
H A Dgithub-automation.py26 This issue may be a good introductory issue for people new to working on LLVM. If you would like to work on this issue, your first steps are:
28 1. Check that no other contributor has already been assigned to this issue. If you believe that no one is actually working on it despite an assignment, ping the person. After one week without a response, the assignee may be changed.
29 1. In the comments of this issue, request for it to be assigned to you, or just create a [pull request](https://github.com/llvm/llvm-project/pulls) after following the steps below. [Mention](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue) this issue in the description of the pull request.
30 1. Fix the issue locally.
34 1. Open a [pull request](https://github.com/llvm/llvm-project/pulls) to the [upstream repository](https://github.com/llvm/llvm-project) on GitHub. Detailed instructions can be found [in GitHub's documentation](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request). [Mention](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue) this issue i
398 def issue(self) -> github.Issue.Issue: global() member in ReleaseWorkflow
[all...]
/llvm-project/llvm/docs/
H A DSecurity.rst15 The LLVM Security Response Group is private. It is composed of trusted LLVM contributors. Its discussions remain within the LLVM Security Response Group (plus issue reporter and key experts) while an issue is being investigated. After an issue becomes public, the entirety of the group’s discussions pertaining to that issue also become public.
17 .. _report-security-issue:
19 How to report a security issue?
22 To report a security issue in any of the LLVM projects, please use the `report a vulnerability`_ feature in the `llvm/llvm-security-repo`_ repository on github, under the "Security" tab.
24 We aim to acknowledge your report within two business days since you first reach out. If you do not receive any response by then, you can escalate by posting on the `Discourse forums`_ asking to get in touch with someone from the LLVM Security Response Group. **The escalation mailing list is public**: avoid discussing or mentioning the specific issue when posting on it.
84 - If already in the LLVM Security Response Group, has actively participated in one (if any) security issue in the last year.
136 Members of the LLVM Security Response Group will be expected to treat LLVM security issue informatio
[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
115 ``Fixes #<issue number>`` on a line by itself. GitHub recognizes such commit
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
[all …]
H A DContributing.rst29 `good first issue`_ keyword in the `bug tracker`_ are a good way to get familiar with
39 Reporting a Security Issue
42 There is a separate process to submit security-related bugs, see :ref:`report-security-issue`.
201 .. _good first issue: https://github.com/llvm/llvm-project/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22
/llvm-project/clang/test/Index/
H A Dreparsed-live-issue.cpp1 …p-file-0=%S/Inputs/reparse-issue.h,%S/Inputs/reparse-issue.h-0 -remap-file-1=%S/Inputs/reparse-iss…
2 #include "Inputs/reparse-issue.h"
4 // CHECK: reparse-issue.h:4:1:{1:1-1:1}: error: a type specifier is required for all declarations
/llvm-project/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/llvm/test/CodeGen/AArch64/
H A Dmisched-bundle.mir17 # CHECK-NEXT: Single Issue : false;
35 # CHECK-NEXT: Single Issue : false;
47 # CHECK-NEXT: Single Issue : false;
59 # CHECK-NEXT: Single Issue : false;
71 # CHECK-NEXT: Single Issue : false;
83 # CHECK-NEXT: Single Issue : false;
104 # CHECK-NEXT: Single Issue : false;
130 # CHECK-NEXT: Single Issue : false;
148 # CHECK-NEXT: Single Issue : false;
165 # CHECK-NEXT: Single Issue
[all...]
/llvm-project/clang/include/clang/Analysis/
H A DIssueHash.h25 /// We may introduce more variants of issue hashes in the future
32 /// - Contents of the line of code with the issue, excluding whitespace.
40 /// Get the unhashed string representation of the V1 issue hash.
41 /// When hashed, it becomes the actual issue hash. Useful for testing.
/llvm-project/clang/test/SemaCXX/
H A Dctad-copy-init-list-narrowing.cpp29 // This is the almost the exact code that was in issue #62925.
34 …d to 'int' in initializer list}} // expected-note {{insert an explicit cast to silence this issue}} in testOneLevelNesting()
42 …d to 'int' in initializer list}} // expected-note {{insert an explicit cast to silence this issue}} in testMultipleLevelNesting()
45 …d to 'int' in initializer list}} // expected-note {{insert an explicit cast to silence this issue}} in testMultipleLevelNesting()
/llvm-project/clang-tools-extra/docs/clang-tidy/checks/bugprone/
H A Dinc-dec-in-conditions.rst32 the code. To fix this issue, the developer should separate the increment
47 Another common issue occurs when multiple increments or decrements are performed
58 There is a potential issue with this code due to the order of evaluation in C++.
66 To avoid this potential issue, the both increment and decrement operation on
H A Dchained-comparison.rst17 To avoid such errors, the check will issue a warning when a chained
38 Even that above issue could be detected as comparison of ``int`` to ``bool``,
55 To avoid this issue, the developer can use a logical operator to separate the
/llvm-project/clang/test/Preprocessor/
H A Delifdef.c44 #elifdef BAR // test that comments aren't an issue
51 #elifdef BAR // test that comments aren't an issue
59 #elifndef BAR // test that comments aren't an issue
66 #elifndef BAR // test that comments aren't an issue
76 #elifdef BAR // test that comments aren't an issue
/llvm-project/clang/include/clang/Basic/
H A DDiagnosticCategories.td9 class CatInlineAsm : DiagCategory<"Inline Assembly Issue">;
10 class CatSourceMgr : DiagCategory<"SourceMgr Reported Issue">;
11 class CatBackend : DiagCategory<"Backend Issue">;
/llvm-project/llvm/include/llvm/CodeGen/
H A DScheduleHazardRecognizer.h55 /// * NoHazard: it is legal to issue this instruction on this cycle.
57 /// other instruction is available, issue it first.
59 /// some other instruction can be issued, do so, otherwise issue a noop.
100 /// instruction to be scheduled cannot issue in the current cycle, either
107 /// instruction to be scheduled cannot issue in the current cycle, either
/llvm-project/compiler-rt/test/ubsan/TestCases/Misc/
H A Dmonitor.cpp8 // Linkage issue
31 printf("Issue: %s\n", IssueKind); in __ubsan_on_report()
42 // CHECK: Issue: invalid-bool-load in main()
/llvm-project/lldb/test/API/lang/objc/print-obj/
H A DTestPrintObj.py47 # other thread to issue our 'po lock_me' command.
61 # Set the other thread as the selected thread to issue our 'po'
70 # issue our 'po lock_me' command.
/llvm-project/compiler-rt/test/asan/TestCases/Darwin/
H A Dduplicate_os_log_reports.cpp49 // ASan's internal syslog buffer was handled after reporting an issue. in main()
51 // after reporting an issue. When another issue was encountered everything in main()
/llvm-project/clang-tools-extra/test/clang-tidy/checkers/bugprone/
H A Dnon-zero-enum-to-bool-conversion.cpp2 …s: {bugprone-non-zero-enum-to-bool-conversion.EnumIgnoreList: '::without::issue::IgnoredEnum;Ignor…
4 namespace with::issue { namespace
43 namespace without::issue { namespace
/llvm-project/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

12345678910>>...57