| /llvm-project/llvm/docs/ |
| H A D | GitHub.rst | 1 .. _github-reviews:
10 `Source Code <https://github.com/llvm/llvm-project>`_,
11 `Releases <https://github.com/llvm/llvm-project/releases>`_,
12 `Issue Tracking <https://github.com/llvm/llvm-project/issues>`_., and
13 `Code Reviews <https://github.com/llvm/llvm-project/pulls>`_.
22 intended to be able to support "stacked" pull-request. Do not create any branches in the
23 llvm/llvm-project repository otherwise, please use a fork (see below). User branches that
24 aren't associated with a pull-reques
64 Creating Pull Requests with GitHub CLICreating Pull Requests global() argument
[all...] |
| H A D | Contributing.rst | 21 ----------
[all...] |
| H A D | MyFirstTypoFix.rst | 26 - know how to use an editor,
28 - have basic C++ knowledge,
30 - know how to install software on your system,
32 - are comfortable with the command line,
34 - have basic knowledge of git.
38 -----
[all...] |
| H A D | CodeReview.rst | 4 LLVM Code-Review Policy and Practices
7 LLVM's code-review policy and practices help maintain high code quality across
15 It is important for all contributors to understand our code-review
16 practices and participate in the code-review process.
22 ------
[all...] |
| H A D | HowToReleaseLLVM.rst | 8 This document contains information about successfully releasing LLVM ---
9 including sub-projects: e.g., ``clang`` and ``compiler-rt`` --- to the public.
21 LLVM is released on a time based schedule --
[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.
10 4. Ensure timely notification and release to vendors who package and distribute LLVM-based toolchains and projects.
11 5. Ensure timely notification to users of LLVM-based toolchains whose compiled code is security-sensitive, through the `CVE process`_.
17 .. _report-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.
31 --
[all...] |
| H A D | DeveloperPolicy.rst | 30 policies <copyright-license-patents>` with contributors to the project.
33 contributing one-off patches can do so in an informal way by sending them to the
34 `llvm-commits mailing list
35 <http://lists.llvm.org/mailman/listinfo/llvm-commits>`_ and engaging another
42 always welcome `one-off patches`_ from people who do not routinely contribute to
49 ----
[all...] |
| H A D | InstCombineContributorGuide.md | 10 Tests for new optimizations or miscompilation fixes should be pre-committed.
15 This means that pull requests should generally contain two commits: First,
23 Exceptions: When fixing assertion failures or infinite loops, do not pre-commit
35 llvm/utils/update_test_checks.py --opt-binary build/bin/opt \
39 Exceptions: Hand-written CHECK lines are allowed for debuginfo tests.
50 optimize in some non-trivial way, you may add it as well -- however, the bulk
54 For example, a test checking multi-use behavior of a fold involving the
58 test all combinations of everything. If you have multi-use tests, and you have
59 commuted tests, you shouldn't also add commuted multi-use tests.
61 Prefer to keep bit-widths for tests low to improve performance of proof checking using alive2. Usin…
[all …]
|
| H A D | GettingStarted.rst | 19 C-like languages use the `Clang <https://clang.llvm.org/>`_ front end. This
21 -- and from there into object files, using LLVM.
34 * ``git clone https://github.com/llvm/llvm-project.git``
37 ``git clone --config core.autocrlf=false
38 https://github.com/llvm/llvm-project.git``
39 * To save storage and speed-up the checkout time, you may want to do a
40 `shallow clone <https://git-scm.com/docs/git-clon
[all...] |
| /llvm-project/.github/workflows/ |
| H A D | issue-write.yml | 6 - "Check code formatting"
7 - "Check for private emails used in PRs"
8 - "PR Request Release Note"
10 - completed
16 pr-comment:
17 runs-on: ubuntu-latest
19 pull-requests
[all...] |
| H A D | new-prs.yml | 1 name: "Labelling new pull requests"
8 # code from the pull request branch.
9 # See https://securitylab.github.com/research/github-actions-preventing-pwn-requests/
12 - opened
13 - reopened
14 - ready_for_review
15 - synchronize
19 runs-on: ubuntu-latest
21 pull-requests: write
26 …# See https://docs.github.com/en/webhooks/webhook-events-and-payloads?actionType=opened#pull_reque…
[all …]
|
| H A D | merged-prs.yml | 8 # code from the pull request branch.
9 # See https://securitylab.github.com/research/github-actions-preventing-pwn-requests/
12 - closed
16 runs-on: ubuntu-latest
18 pull-requests: write
19 if: >-
20 (github.repository == 'llvm/llvm-project') &&
23 - name: Checkout Automation Script
26 sparse-checkout: llvm/utils/git/
29 - name: Setup Automation Script
[all …]
|
| H A D | issue-release-workflow.yml | 4 # /cherry-pick <commit> <...>
6 # This comment will attempt to cherry-pick the given commits to the latest
12 # This comment will create a pull request from <branch> to the latest release
23 - created
24 - edited
27 - opened
33 backport-commits:
35 runs-on: ubuntu-latest
38 pull-requests: write
39 if: >-
[all …]
|
| H A D | docs.yml | 4 # SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
14 - 'main'
16 - 'llvm/docs/**'
17 - 'clang/docs/**'
18 - 'clang/include/clang/Basic/AttrDocs.td'
19 - 'clang/include/clang/Driver/ClangOptionDocs.td'
20 - 'clan
[all...] |
| /llvm-project/llvm/utils/git/ |
| H A D | github-automation.py | 3 # ======- github-automation - LLVM GitHub Automation Routines--*- python -*--==#
7 # SPDX-Licens
[all...] |
| /llvm-project/flang/docs/ |
| H A D | PullRequestChecklist.md | 1 <!--===- docs/PullRequestChecklist.md
5 SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
7 -->
9 # Pull request checklist
10 Please review the following items before submitting a pull request. This list
11 can also be used when reviewing pull requests.
27 * When submitting an update to a pull request, review previous pull request
34 * Run clang-format using the git-clang-format script from LLVM HEAD.
36 clang-format will do this for most code. But you may need to break up long
46 * Declare non-member functions ```static``` when possible. Prefer
|
| /llvm-project/libcxx/docs/ |
| H A D | Contributing.rst | 14 Looking for pre-existing pull requests
17 Before you start working on any feature, please take a look at the open libc++ pull
18 requests to avoid duplicating someone else's work. You can do that on GitHub by
19 filtering pull requests `tagged with libc++ <https://github.com/llvm/llvm-project/pulls?q=is%3Apr+is%3Aopen+label%3Alibc%2B%2B>`__.
23 RFCs for significant user-affecting changes
49 -
[all...] |
| /llvm-project/libc/src/math/docs/ |
| H A D | add_math_function.md | 1 # How to add a new math function to LLVM-libc
14 - Add entry points `libc.src.math.func` to the following files:
19 - Add function specs to the file:
29 - Add `add_math_entrypoint_object(<func>)` to:
33 - Add function declaration (under `LIBC_NAMESPACE` namespace) to:
37 - Add function definition to:
41 - Add the corresponding `add_entrypoint_object` to:
45 - Add architectural specific implementations to:
52 - Floating point utilities and math functions that are also used internally are
57 - Thes
[all...] |
| /llvm-project/clang-tools-extra/clangd/ |
| H A D | ClangdServer.h | 1 //===--- ClangdServer.h - Main clangd server code ------
[all...] |
| H A D | Protocol.h | 1 //===--- Protocol.h - Language Server Protocol Implementation ---*- C++ -*-
[all...] |
| /llvm-project/llvm/include/llvm/Support/ |
| H A D | Allocator.h | 1 //===- Allocator.h - Simple memory allocation abstraction -------*-
[all...] |
| /llvm-project/llvm/docs/Proposals/ |
| H A D | GitHubMove.rst | 22 infrastructure) will continue to work with a Git-based LLVM.
29 This proposal relates only to moving the hosting of our source-code repository
31 using GitHub's issue tracker, pull-requests, or code-review.
35 username/password-hash.
41 ----------------
57 --------
66 through the Git-SVN integration.
82 -----------
85 projects. Any of these could replace the code-hosting infrastructure that we
92 BitBucket: it offers read-write **SVN** access to the repository
[all …]
|
| /llvm-project/lldb/packages/Python/lldbsuite/test/tools/lldb-server/ |
| H A D | lldbgdbserverutils.py | 1 """Module for supporting unit testing of the lldb-server debug monitor exe.
26 """Return the lldb-server exe path.
29 A path to the lldb-server exe if it is found to exist; otherwise,
33 return _get_support_exe("lldb-server")
54 r"^(lldb-server|debugserver)\s+<\s*(\d+)>\s+(read|send)\s+packet:\s+(.+)$"
59 """Return whether a given packet is input for lldb-gdbserver.
65 llgs_input_is_read: true if lldb-gdbserver input (content sent to
66 lldb-gdbserver) is listed as 'read' or 'send' in the packet
70 True if the packet should be considered input for lldb-gdbserver; False
86 _STRIP_CHECKSUM_REGEX = re.compile(r"#[0-9a-fA-F]{2}$")
[all …]
|
| /llvm-project/lldb/source/Plugins/Process/FreeBSD/ |
| H A D | NativeProcessFreeBSD.cpp | 1 //===-- NativeProcessFreeBSD.cpp --------
[all...] |
| /llvm-project/lldb/source/Plugins/Process/NetBSD/ |
| H A D | NativeProcessNetBSD.cpp | 1 //===-- NativeProcessNetBSD.cpp --------
[all...] |