summaryrefslogtreecommitdiffstats
path: root/util/system
Commit message (Collapse)AuthorAgeFilesLines
* Correct debug trap for M1somov2022-10-301-0/+4
|
* Remove a workaround for ancient CUDA versionsdfyz2022-10-291-7/+0
| | | `#define noexcept throw()` is a questionable idea, since replacing `noexcept` with `throw()` in expressions such as `noexcept(true)` results in spectacular compiler errors. We stopped supporting CUDA 8 (and even CUDA 9) long ago, which means we can just get rid of the problematic define.
* Enable linux-arm platform.dcherednik2022-10-261-0/+52
|
* Fix a warning when compiling util/ with nvcc 10.xdfyz2022-10-081-1/+1
| | | | | | | | | | | | nvcc10.1 is unable to compile `[[clang::reinitializes]]` and issues warning as follows: ``` util/generic/ptr.h(194): warning: attribute namespace "clang" is unrecognized util/generic/ptr.h(201): warning: attribute namespace "clang" is unrecognized [...] ``` nvcc11 compiles this code without any warnings. This PRs disable `[[clang::reinitialized]]` when compiling with nvcc10.
* Clang14: Fix library/cpp/coroutine/engine under tsanpg2022-09-291-1/+3
|
* add comment for TAdaptiveLocktobo2022-09-221-0/+8
| | | https://clubs.at.yandex-team.ru/arcadia/8450/8489#reply-arcadia-8489
* Fix tsan warnings in yt intrusive ptrayles2022-09-191-0/+21
| | | | | | | | | | | | | | | | | | | | | For example, https://github.com/google/sanitizers/issues/1352 - tsan is not working well with std::atomic_thread_fence Minimal reproducible example (and one that bothers most in every fiber-aware service): ``` auto threadPool = NYT::New<NYT::NConcurrency::TThreadPool>(2, "thread"); TVector<NYT::TFuture<void>> futures; for (size_t i = 0; i < 100000; ++i) { futures.emplace_back(BIND([]() { }).AsyncVia(threadPool->GetInvoker()).Run()); } for (auto& future : futures) { future.Get().ThrowOnError(); } ```
* Fix incorrect fqdn on linux in some edge casessnaury2022-09-021-9/+28
|
* fixup size of aligned memory region to mlock []yurial2022-08-301-2/+17
| | | Если мы сдвигаем addr в меньшую сторону, то len мы должны увеличить на столько же. В противном случае, мы можем залочить меньше, чем нужно.
* Mark clear and reset methods as reinitializing the object.halyavin2022-08-051-0/+6
| | | | | This means, that moved-from object can be safely used after the call of such method. This attribute is used by clang-tidy which checks that moved-from objects are not used unless a reinitialization method is called first.
* fix ya.makemonster2022-07-0710-609/+0
|
* Allow creating Singlelon during Singleton destruction back againthegeorg2022-06-242-1/+21
| | | | ref:53c837a1fa0289db60812b95b6ac96be23ae018d
* IGNIETFERRO-1922 Move atomics from util to library/cpp/deprecatedeeight2022-06-158-682/+6
| | | | ref:0c3b0edd3284567c45ec77e57166274f3cfed8c7
* util: Flatten cython tests layoutthegeorg2022-06-031-0/+12
| | | | ref:7427208d08ebeb9e88247fb7dac6445bc814d756
* IGNIETFERRO-1105 Get rid of TAtomic in spin_waiteeight2022-05-231-10/+13
| | | | ref:788357fd9a851f54e97a8e0f133dcb3c3e275f92
* IGNIETFERRO-1105 Get rid of TAtomic in system/{atexit, event, shellcommand}eeight2022-05-205-39/+57
| | | | ref:c74bffae7e90dee515f5089979fc050d20a34e4e
* IGNIETFERRO-1105 Get rid of TAtomic in unittestseeight2022-05-194-78/+58
| | | | ref:f4d9cf527b4f26efcc95307ca7b07d1c42ebd11b
* IGNIETFERRO-1105 Use std::atomic in spinlockeeight2022-05-173-56/+49
| | | | ref:dca14f354fc9b9698f83663ceb0e62e797fe98c5
* remove unused includestobo2022-04-0730-84/+18
| | | | ref:f8c119cf3a796a59ab5be4424e5364ba6a201d40
* util: Fix -Wunused-but-set-variablekmartynkov2022-03-231-2/+0
| | | | ref:0186c219d9c56c8f183ce0236e33f6d647fe5fa0
* util: Do not define SIZEOF_SIZE_T, as it is not used in our codebasethegeorg2022-03-202-5/+1
| | | | | | | | | | | | | | codesearch shows [114 usages](https://a.yandex-team.ru/search?search=%5CbSIZEOF_SIZE_T%5Cb,,jC,arcadia,,500) of this macro outside of contrib. None of these usages looks as being util-dependent. Defining this in util triggers `-Wmacro-redefined` whenever `` gets included after our ``. UPD: It turns out that our curl was using this define for a reason, so I have implemented an util-independent solution instead. ref:c80e45c42a9c0ec76eda33e63b560b285e1ee502
* Remove read-only files and directories on Windows (to match behavior on unix)setser2022-03-162-0/+75
| | | | | | | | | | Current behavior of RemoveDirWithContents does not allow removing directories if any of files in this directory is read-only. This behavior, however, does not allow, for example, to remove temporary directory, in which git repository was created (on *nix systems, however, this problem was not noticed). This PR overrides this behavior. ref:1faf91e233008b4aece4f2b953884b52346ce2be
* intermediate changesarcadia-devtools2022-03-159-200/+0
| | | | ref:ca7a95e8c9a9d780f96497136a152091d54e61b5
* Fix -Wpragma-pack in trie.hthegeorg2022-03-071-1/+13
| | | | | | | | | | `#include ` and `#include ` modify current `#pragma pack` value and thus trigger `-Wpragma-pack` under clang-cl. As there is no way to implement packed structs via attributes, introduce proper compiler-specific variables in `` and use them to check whether we are compiling with MSVC. ref:e47cdb9c38eb305b9c5bcc5ad719e21ec52eb14c
* rm unused includestobo2022-03-051-8/+0
| | | | ref:b9f56a64ccc7a4f4980fa176af362932c04214b3
* Enable yet another warning under clang-clthegeorg2022-03-032-37/+50
| | | | ref:fdd92250532d24eebbf27cb8f8369eeb88e17df9
* Support std::filesystem::path in Arcadia streamsthegeorg2022-03-031-1/+1
| | | | ref:11bbdd83544b9579747dd12d51395840bda86faf
* clang-tidy - move-constructor and move-assignment operators should be marked ↵tobo2022-02-282-2/+2
| | | | | | noexcept + pass some args by reference ref:5da43163e6b3c2499597234dc80ad47042259013
* rm unused includetobo2022-02-251-1/+0
| | | | ref:98e6837fcfff74a0af567f24b8c63f3353a501a1
* fix CLion perf warnings - use const references instead of passing by valuetobo2022-02-244-20/+21
| | | | ref:e94e72a813a3aa41c543fd1d9f7d73f02cca8bc0
* rm unused includetobo2022-02-221-1/+0
| | | | ref:f0f0572f52d7977841789105c6b51d4ca5ea1382
* Properly attribute err.h replacements as [[noreturn]]thegeorg2022-02-192-9/+12
| | | | ref:e86419934a6858c3f36f45e15d1e42cc501ea395
* pass string by reference, rm unused includetobo2022-02-192-3/+2
| | | | ref:b2a9abb354b18c7a8d339a26c1e23fba39e48c06
* [util] fix fstat for archive directories on windowskikht2022-02-174-32/+154
| | | | | | | | | | | | | | | | | | | Currently TFileStat has a bunch of problems on Windows: 1. Mode computation ORs different types, but file attributes it checks are not mutually exclusive. E.g. it is possible for directory to have both `FILE_ATTRIBUTE_DIRECTORY` and `FILE_ATTRIBUTE_ARCHIVE`, but it will currently lead to invalid `_S_IFDIR | _S_IFREG` mode. 2. Any file with `FILE_ATTRIBUTE_REPARSE_POINT` flag is considered to be symlink. But there are many other types of reparse points even user-defined ones. For more info see https://docs.microsoft.com/en-us/windows/win32/fileio/reparse-point-tags To fix all this we do the following: 1. Add `ReparseTag` field to `TSystemFStat` and fill it for reparse points in `GetStatByHandle`. 2. Refactor `GetWinFileType` out of `GetFileMode` to ensure that we always select only single `S_IFMT` value. 3. Pass reparse tag value into `GetWinFileType` and select `S_IFLNK` only for `IO_REPARSE_TAG_SYMLINK` and `IO_REPARSE_TAG_MOUNT_POINT` tags. The latter one is a bit strange, but this behaviour is aligned with current implementation of `WinReadLink`. 4. Factor `ReadReparsePoint` out of `WinReadLink`. This function uses `DeviceIoControl` to read reparse point data into structures copied from WDK. 5. Add `WinReadReparseTag` that uses `ReadReparsePoint` to extract reparse point tag. We use this approach instead of MSDN-recommended `FindFirstFile` because latter requires file path, but we have file handle at this point. AFAIK golang and python use similar approach for this. 6. Add test for archived directory case. 7. Make symlink nofollow tests run only when symlink creation is possible for current user. Discovered in https://st.yandex-team.ru/ARC-3931 ref:4f6735817b9f85f3351a1021a56dd7eb4606bd65
* TShellCommand::TImpl via TShellCommandOptionsgleb-kov2022-02-172-96/+65
| | | | ref:f149c0bc76521a1273f6a2c155f2bd116141b1eb
* Restoring authorship annotation for <[email protected]>. Commit 2 of 2.vsevolod2022-02-101-6/+6
|
* Restoring authorship annotation for <[email protected]>. Commit 1 of 2.vsevolod2022-02-101-6/+6
|
* Restoring authorship annotation for <[email protected]>. Commit 2 of 2.pzuev2022-02-101-1/+1
|
* Restoring authorship annotation for <[email protected]>. Commit 1 of 2.pzuev2022-02-101-1/+1
|
* Restoring authorship annotation for <[email protected]>. Commit 2 of 2.the02022-02-101-1/+1
|
* Restoring authorship annotation for <[email protected]>. Commit 1 of 2.the02022-02-101-1/+1
|
* Restoring authorship annotation for <[email protected]>. Commit 2 of 2.immartynov2022-02-103-24/+24
|
* Restoring authorship annotation for <[email protected]>. Commit 1 of 2.immartynov2022-02-103-24/+24
|
* Restoring authorship annotation for <[email protected]>. Commit 2 ↵marat-khalili2022-02-102-24/+24
| | | | of 2.
* Restoring authorship annotation for <[email protected]>. Commit 1 ↵marat-khalili2022-02-102-24/+24
| | | | of 2.
* Restoring authorship annotation for <[email protected]>. Commit 2 of 2.pppp2022-02-101-21/+21
|
* Restoring authorship annotation for <[email protected]>. Commit 1 of 2.pppp2022-02-101-21/+21
|
* Restoring authorship annotation for <[email protected]>. Commit 2 of 2.alyashko2022-02-101-86/+86
|
* Restoring authorship annotation for <[email protected]>. Commit 1 of 2.alyashko2022-02-101-86/+86
|
* Restoring authorship annotation for <[email protected]>. Commit 2 of 2.muzykantov2022-02-102-23/+23
|
generated by cgit v1.2.3 (git 2.25.1) at 2025-10-06 00:03:31 +0000