| /llvm-project-15.0.7/compiler-rt/lib/sanitizer_common/ |
| H A D | sanitizer_linux_s390.cpp | 131 unsigned int major, minor, patch = 0; in FixedCVE_2016_2143() local 143 patch = internal_simple_strtoll(ptr+1, &ptr, 10); in FixedCVE_2016_2143() 145 if (major == 2 && minor == 6 && patch == 32 && ptr[0] == '-' && in FixedCVE_2016_2143() 161 if (minor == 2 && patch >= 79) in FixedCVE_2016_2143() 164 if (minor == 12 && patch >= 58) in FixedCVE_2016_2143() 166 if (minor == 10 && patch == 0 && ptr[0] == '-' && in FixedCVE_2016_2143() 182 if (minor == 1 && patch >= 21) in FixedCVE_2016_2143() 185 if (minor == 4 && patch >= 6) in FixedCVE_2016_2143() 187 if (minor == 4 && patch == 0 && ptr[0] == '-' && in FixedCVE_2016_2143()
|
| H A D | sanitizer_linux_libcdep.cpp | 173 int *patch) { in GetLibcVersion() argument 186 *patch = (*p == '.') ? internal_simple_strtoll(p + 1, &p, 10) : 0; in GetLibcVersion() 204 int major, minor, patch; in InitTlsSize() local 206 GetLibcVersion(&major, &minor, &patch) && major == 2 && minor >= 25; in InitTlsSize() 231 int patch; in ThreadDescriptorSizeFallback() local 232 if (GetLibcVersion(&major, &minor, &patch) && major == 2) { in ThreadDescriptorSizeFallback() 249 else if (minor == 11 || (minor == 12 && patch == 1)) in ThreadDescriptorSizeFallback() 271 int patch; in ThreadDescriptorSizeFallback() local 272 if (GetLibcVersion(&major, &minor, &patch) && major == 2) { in ThreadDescriptorSizeFallback()
|
| /llvm-project-15.0.7/llvm/docs/ |
| H A D | CodeReview.rst | 33 uncertainty, a patch should be reviewed prior to being committed. 35 Please note that the developer responsible for a patch is also 47 the patch to be :ref:`reverted <revert_policy>`. 55 code in the tree. This does not indicate any fault from the patch author, 74 original change was committed, it may be better to create a new patch to 104 approval, or solicit objections to a patch with a deadline. 152 the patch (which literally means submitting a comment on the patch with the 179 patches for independent review. Reviewers may also accept a patch 180 conditioned on the author providing a follow-up patch addressing some 226 for an expert to review the patch or review it yourself. [all …]
|
| H A D | Phabricator.rst | 61 will also run on every patch update: 96 to upload your patch): 98 * ``git show HEAD -U999999 > mypatch.patch`` 105 To upload a new patch: 121 To submit an updated patch: 138 .. _creating-a-patch-series: 140 Creating a patch series 157 * This will open a dialog where you will enter the patch number of the parent patch 170 .. _using-patch-summaries: 172 Using patch summaries [all …]
|
| H A D | Contributing.rst | 55 Once you have a patch ready, it is time to submit it. The patch should: 65 Before sending a patch for review, please also try to ensure it is 96 To make sure the right people see your patch, please select suitable reviewers 97 and add them to your patch when requesting a review. Suitable reviewers are the 99 patch touches. If you are using Phabricator, add them to the `Reviewers` field 106 updated version of your patch. This cycle continues until all requests and comments 107 have been addressed and a reviewer accepts the patch with a `Looks good to me` or `LGTM`. 112 If you have received no comments on your patch for a week, you can request a 113 review by 'ping'ing a patch by responding to the email thread containing the 114 patch, or the Phabricator review with "Ping." The common courtesy 'ping' rate [all …]
|
| H A D | StackMaps.rst | 2 Stack maps and patch points in LLVM 30 A patch point is an instruction address at which space is reserved for 70 maps and patch points: ``llvm.experimental.stackmap`` and 138 patch the code at this point in response to an event triggered from 169 patch 8 bytes of code at the stack map's address at follows: 217 The patch point intrinsic generates a stack map. It also emits a 229 Requesting zero patch point arguments is valid. In this case, all 245 The patch point also emits nops to cover at least ``<numBytes>`` of 252 The runtime may patch the code emitted for the patch point, including 255 patching is not allowed. The runtime must patch all reserved bytes, [all …]
|
| H A D | DeveloperPolicy.rst | 78 #. Make your patch against git main, not a branch, and not an old version 85 time the patch was created and the time it is applied. 90 #. Once you have created your patch, create a 291 revert or reapply of a patch, include the git commit hash of the prior 319 original commit thread with the reverting patch author. 326 fixed patch - possibly after another round of review if warranted. 344 problematic patch will be reverted and we can return to it at our next 355 the proper patch or set of patches is being reverted. 356 * The commit message for the reverting commit should explain why patch 597 other patch. [all …]
|
| /llvm-project-15.0.7/polly/lib/External/isl/doc/ |
| H A D | SubmittingPatches | 25 - use "git format-patch -M" to create the patch 26 - do not PGP sign your patch 27 - send a single patch per mail, e.g., using git-send-email(1) 28 - do not attach your patch, but read in the mail 30 leave the formatting of the patch alone. 40 - send the patch to the development mailing list 49 when creating the patch)
|
| /llvm-project-15.0.7/llvm/include/llvm/Demangle/ |
| H A D | DemangleConfig.h | 36 #define DEMANGLE_GNUC_PREREQ(maj, min, patch) \ argument 38 ((maj) << 20) + ((min) << 10) + (patch)) 40 #define DEMANGLE_GNUC_PREREQ(maj, min, patch) \ argument 43 #define DEMANGLE_GNUC_PREREQ(maj, min, patch) 0 argument
|
| /llvm-project-15.0.7/libcxxabi/src/demangle/ |
| H A D | DemangleConfig.h | 41 #define DEMANGLE_GNUC_PREREQ(maj, min, patch) \ argument 43 ((maj) << 20) + ((min) << 10) + (patch)) 45 #define DEMANGLE_GNUC_PREREQ(maj, min, patch) \ argument 48 #define DEMANGLE_GNUC_PREREQ(maj, min, patch) 0 argument
|
| /llvm-project-15.0.7/llvm/test/CodeGen/PowerPC/ |
| H A D | ppc-redzone-alignment-bug.ll | 2 ; after patch https://reviews.llvm.org/D34337, we could save 16 bytes in the best case. 10 ; Before the fix by patch D34337: 18 ; After the fix by patch D34337:
|
| /llvm-project-15.0.7/libcxx/docs/ |
| H A D | Contributing.rst | 51 After uploading your patch, you should see that the "libc++" review group is automatically 52 added as a reviewer for your patch. Once the group is marked as having approved your patch, 53 you can commit it. However, if you get an approval very quickly for a significant patch, 55 other reviewers to chime in. If you need someone else to commit the patch for you, please 59 of the group to have approved the patch, excluding the patch author. This is not a hard
|
| /llvm-project-15.0.7/compiler-rt/test/asan/TestCases/Darwin/ |
| H A D | cstring_literals_regtest.mm | 12 int major = 0, minor = 0, build = 0, patch = 0; 18 major, minor, build, patch];
|
| /llvm-project-15.0.7/llvm/include/llvm/Support/ |
| H A D | Compiler.h | 61 # define LLVM_GNUC_PREREQ(maj, min, patch) \ argument 63 ((maj) << 20) + ((min) << 10) + (patch)) 65 # define LLVM_GNUC_PREREQ(maj, min, patch) \ argument 68 # define LLVM_GNUC_PREREQ(maj, min, patch) 0 argument
|
| /llvm-project-15.0.7/pstl/ |
| H A D | CREDITS.txt | 2 (Parallel STL) project. If you have contributed a patch or made some other 3 contribution to LLVM/pstl, please submit a patch to this file to add yourself,
|
| /llvm-project-15.0.7/lldb/test/Shell/ScriptInterpreter/Python/Crashlog/ |
| H A D | json.test | 4 # RUN: %python %S/patch-crashlog.py --binary %t.out --crashlog %t.crash --offsets '{"main":20, "bar… 8 # RUN: %python %S/patch-crashlog.py --binary %t.out --crashlog %t.nometadata.crash --offsets '{"mai…
|
| /llvm-project-15.0.7/compiler-rt/ |
| H A D | CREDITS.TXT | 2 project. If you have contributed a patch or made some other contribution to 3 LLVM/CompilerRT, please submit a patch to this file to add yourself, and it will be
|
| /llvm-project-15.0.7/polly/ |
| H A D | CREDITS.txt | 2 If you have contributed a patch or made some other contribution to 3 Polly, please submit a patch to this file to add yourself, and it will be
|
| /llvm-project-15.0.7/clang/test/ExtractAPI/ |
| H A D | objc_protocol.m | 29 "patch": 3 41 "patch": 0
|
| /llvm-project-15.0.7/lldb/test/API/functionalities/postmortem/FreeBSDKernel/tools/ |
| H A D | README.rst | 15 3. Patch libfbsdvmcore using ``libfbsdvmcore-hacks.patch`` and build LLDB 18 4. Patch LLDB using ``lldb-minimize-processes.patch`` and build it.
|
| /llvm-project-15.0.7/libcxxabi/ |
| H A D | CREDITS.TXT | 2 project. If you have contributed a patch or made some other contribution to 3 LLVM/libc++abi, please submit a patch to this file to add yourself, and it will be
|
| /llvm-project-15.0.7/openmp/ |
| H A D | CREDITS.txt | 2 project. If you have contributed a patch or made some other contribution to 3 LLVM/openmp, please submit a patch to this file to add yourself, and it will be
|
| /llvm-project-15.0.7/.github/ |
| H A D | PULL_REQUEST_TEMPLATE.md | 3 …sts. Please follow http://llvm.org/docs/Contributing.html#how-to-submit-a-patch for contribution t…
|
| /llvm-project-15.0.7/llvm/cmake/modules/ |
| H A D | LLVMConfigVersion.cmake.in | 4 # and patch versions not less than that requested.
|
| /llvm-project-15.0.7/.github/workflows/ |
| H A D | repo-lockdown.yml | 19 …Please follow http://llvm.org/docs/Contributing.html#how-to-submit-a-patch for contribution to LLV…
|