llvm-project.git/libc/src/__support/threads/fork_callbacks.cpp, branch users/nico/python-2

[libc] Migrate to using LIBC_NAMESPACE_DECL for namespace declaration (#98597)

2024-07-12T16:28:41+00:00

This is a part of #97655.

Revert "[libc] Migrate to using LIBC_NAMESPACE_DECL for namespace declaration" (#98593)

2024-07-12T07:12:13+00:00

Reverts llvm/llvm-project#98075

bots are broken

[libc] Migrate to using LIBC_NAMESPACE_DECL for namespace declaration (#98075)

2024-07-11T19:35:22+00:00

This is a part of #97655.

[libc] rework mutex (#92168)

2024-06-01T01:57:18+00:00

[libc] Replace `MutexLock` with `cpp::lock_guard` (#89340)

2024-05-09T07:06:18+00:00

This PR address issue #89002.

#### Changes in this PR

* Added a simple implementation of `cpp::lock_guard` (an equivalent of
`std::lock_guard`) in libc/src/__support/CPP inspired by the libstdc++
implementation
* Added tests for `cpp::lock_guard` in
/libc/test/src/__support/CPP/mutex_test.cpp
* Replaced all references to `MutexLock` with `cpp::lock_guard`

---------

Co-authored-by: Guillaume Chatelet

[libc] Mass replace enclosing namespace (#67032)

2023-09-26T09:45:04+00:00

This is step 4 of
https://discourse.llvm.org/t/rfc-customizable-namespace-to-allow-testing-the-libc-when-the-system-libc-is-also-llvms-libc/73079

[libc] move fork into threads folder

2022-11-12T00:01:39+00:00

Fork, as a thread function, should go in the threads folder.
Additionally, it depends on the thread mutex, and it was causing build
issues for targets where we don't support threads.

Reviewed By: lntue

Differential Revision: https://reviews.llvm.org/D137867