- Mar 01, 2025
-
-
1079929c Status: Fix encoding of error strings on Windows Acked-by:
Kitware Robot <kwrobot@kitware.com> Merge-request: !330
-
- Feb 28, 2025
-
-
- Feb 12, 2025
-
-
2f654745 SystemInformation: Let NumberOf{Physical,Logical}CPU respect each other Acked-by:
-
- Feb 11, 2025
-
-
Xeonacid authored
-
6b6ab811 SystemTools: Revert "use CopyFile on Windows" Acked-by:
-
-
6958dea7 SystemTools: use CopyFile on Windows Acked-by:
-
- Feb 10, 2025
-
-
-
a13d90c2 SystemInformation: use HW_NCPUONLINE on OpenBSD and NetBSD Acked-by:
-
- Feb 09, 2025
-
-
Brad Smith authored
-
- Feb 07, 2025
-
-
22af8b25 SystemTools: Fix invalid memory access in ConvertToUnixSlashes 2ab910a3 SystemTools: Improve repeated slash handling in ConvertToUnixSlashes Acked-by:
-
- Feb 06, 2025
-
-
Nikita Nemkin authored
Don't use npos as an index. But passing it to substr() and doing arithmetic with it is safe. Remove unnecessary use of c_str() for extra safety. Issue: cmake/cmake#26667
-
Nikita Nemkin authored
Collapse repeated slashes, but preserve exactly two leading slashes. POSIX reserves exactly two leading slashes for implementation-defined behavior. On Windows and Cygwin they mark UNC paths. Improve test coverage of ConvertToUnixSlashes. Issue: cmake/cmake#9182
-
- Jan 30, 2025
-
-
08b9f90d Use lower case style for CMake commands Acked-by:
-
- Jan 29, 2025
-
-
8142980e Process: Revert "Add function to get parent PID" a298a4aa Process: Suppress PID conversion warning Acked-by:
-
-
Brad King authored
-
- Jan 28, 2025
-
-
Peter Kokot authored
-
9727dfdb ProcessUNIX: Add function to get parent PID fda58f27 Process.h.in: Add missing undef for Process_KillPID Acked-by:
-
3489e4a2 Encoding: Reformulate to avoid unsigned int overflow Acked-by:
-
c8f5f4bf RegularExpression: Add an options parameter to find() d022423b RegularExpression: Add a method to query the number of capture groups 46fc21ef RegularExpression: Remove redundant overloads Acked-by:
-
- Jan 27, 2025
-
-
Martin Duffy authored
-
Martin Duffy authored
-
Nikita Nemkin authored
There are two options: * BOL_AT_OFFSET enables matching the "^" anchor at the search start position instead of the input start. This is the legacy CMake behavior. * NONEMPTY_AT_OFFSET rejects empty matches at the search start position. This is used to allow zero-length matches when searching for multiple match occurrences. Issue: cmake/cmake#26629
-
Nikita Nemkin authored
This can be used to check for invalid (too high) group references. Issue: cmake/cmake#26629
-
Nikita Nemkin authored
This also makes RegexMatchResult::start/end to reliably report npos for failed matches. Note that start/end of individual capture groups might still contain data even if the match has failed overall. Issue: cmake/cmake#26629
-
Playing with clang UBSan unsigned-integer-overflow I found just 2 warnings in KWSys. They are not undefined behaviour, but often unintentional. A reformulation to avoid the overflow was pretty straightforward. Also noticed and changed `&v[0]` idiom to `v.data()`.
-
0359bfbc RegularExpression: Fix match start/end values of unmatched groups 98452164 RegularExpression: Add an optional offset parameter to find() Acked-by:
-
- Jan 24, 2025
-
-
CMake assumes that Match::start(n) and end(n) return npos for unmatched groups. Make it so and prevent undefined behavior (pointer overflow). Issue: cmake/cmake#16899
-
Separating the search start position from the input start is necessary to correctly implement the "^" anchor when searching for multiple matches in the same string. Issue: cmake/cmake#16899
-
7dec9555 Revise C++ coding style using clang-format with "east const" ac2b3378 Empty commit at end of history preceding clang-format "east const" transition a234f2ff clang-format: Enforce "east const" qualifier placement 7a19509c Revise C++ coding style using clang-format-18 6da5c6ac Empty commit at end of history preceding clang-format-18 style transition a42b7759 clang-format.bash: update to clang-format-18 Acked-by:
-
4a126278 clang-format.bash: Preserve CRLF line endings on Windows Acked-by:
-
- Jan 23, 2025
-
-
Run the `clang-format.bash` script to update all our C and C++ code to a new style defined by `.clang-format`, now with "east const" enforcement. Use `clang-format` version 18. * If you reached this commit for a line in `git blame`, re-run the blame operation starting at the parent of this commit to see older history for the content. * See the parent commit for instructions to rebase a change across this style transition commit.
-
Brad King authored
This is an empty commit that precedes an automatic application of clang-format with "east const" to update the C++ style of our entire source tree. This may be helpful to rebase a topic branch that was originally based on a commit preceding the transition. One may first rebase the topic on this commit. Then use one of the following approaches. * Rewrite the topic, including this commit, using `git filter-branch` `--tree-filter` with `clang-format.bash` to update the style in every commit. Rebase the revised topic, excluding the rewrite of this commit, on the style transition commit. OR * Add a `.git/info/grafts` entry to change the parent of the first commit in the topic from this commit to the style transition commit. Rewrite the topic using `git filter-branch --tree-filter` with `clang-format.bash` to update the style in every commit. Then remove the graft, which was resolved by the filter. See `git help filter-branch` and `git help repository-layout` for details. -
Brad King authored
-
Run the `clang-format.bash` script to update all our C and C++ code to a new style defined by `.clang-format`. Use `clang-format` version 18. * If you reached this commit for a line in `git blame`, re-run the blame operation starting at the parent of this commit to see older history for the content. * See the parent commit for instructions to rebase a change across this style transition commit.
-
Brad King authored
This is an empty commit that precedes an automatic application of clang-format-18 to update the C++ style of our entire source tree. This may be helpful to rebase a topic branch that was originally based on a commit preceding the transition. One may first rebase the topic on this commit. Then use one of the following approaches. * Rewrite the topic, including this commit, using `git filter-branch` `--tree-filter` with `clang-format.bash` to update the style in every commit. Rebase the revised topic, excluding the rewrite of this commit, on the style transition commit. OR * Add a `.git/info/grafts` entry to change the parent of the first commit in the topic from this commit to the style transition commit. Rewrite the topic using `git filter-branch --tree-filter` with `clang-format.bash` to update the style in every commit. Then remove the graft, which was resolved by the filter. See `git help filter-branch` and `git help repository-layout` for details. -
Brad King authored
The `.clang-format` configuration needs no changes to make the version 18 format close to what version 15 produced before.
-
Nikita Nemkin authored
Use the binary mode of GNU sed.
-
- Jan 22, 2025
-
-
e1aeb61e SystemInformation: Fix GetNumberOfLogicalCPU on s390x Acked-by:
-
