vasilito
48a924c561
The libredox 0.1.19 / redox_syscall 0.9.1 bump left 45 recipe lockfiles pinning libredox 0.1.18+rb0.3.1 and redox_syscall 0.9.0+rb0.3.1. The cookbook builds with --locked, so every affected recipe died with error: cannot update the lock file .../Cargo.lock because --locked was passed to prevent this which is what took out redox-driver-sys -- and with it every Red Bear driver -- during the redbear-full build. Regenerating the fork lockfiles was not enough; the recipes that consume the forks as path deps carry their own. This is step 6 of local/docs/FORK-BUMP-PATCHING-POLICY.md applied to the recipe layer. Also drop the hardcoded GCC version in recipes/libs/libstdcxx-v3: the literal include/c++/13.2.0 stopped resolving the moment the cross toolchain moved to 16.1.0, leaving -I pointing at a directory that does not exist. Now resolves the newest installed C++ header directory and fails loudly if there is none. Same failure class as the hardcoded 13.2.0 in mk/prefix.mk. Note: a few recipe-level Cargo.lock files (redox-driver-pci, cpufreqd, redbear-acmd/-ecmd/-ftdi) sit beside a recipe.toml whose [source] is path = "source", so they are not build inputs; redox-driver-pci's even references a redox-driver-core/Cargo.toml that does not exist. They are left alone rather than given meaning they do not have. redox-driver-sys now cooks clean.
58 lines
1.9 KiB
C
58 lines
1.9 KiB
C
/* Copyright (C) 2005-2026 Free Software Foundation, Inc.
|
|
Contributed by Richard Henderson <rth@redhat.com>.
|
|
|
|
This file is part of the GNU Offloading and Multi Processing Library
|
|
(libgomp).
|
|
|
|
Libgomp is free software; you can redistribute it and/or modify it
|
|
under the terms of the GNU General Public License as published by
|
|
the Free Software Foundation; either version 3, or (at your option)
|
|
any later version.
|
|
|
|
Libgomp is distributed in the hope that it will be useful, but WITHOUT ANY
|
|
WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
|
|
FOR A PARTICULAR PURPOSE. See the GNU General Public License for
|
|
more details.
|
|
|
|
Under Section 7 of GPL version 3, you are granted additional
|
|
permissions described in the GCC Runtime Library Exception, version
|
|
3.1, as published by the Free Software Foundation.
|
|
|
|
You should have received a copy of the GNU General Public License and
|
|
a copy of the GCC Runtime Library Exception along with this program;
|
|
see the files COPYING3 and COPYING.RUNTIME respectively. If not, see
|
|
<http://www.gnu.org/licenses/>. */
|
|
|
|
/* This file contains helpers for the ATOMIC construct. */
|
|
|
|
#include "libgomp.h"
|
|
|
|
/* This mutex is used when atomic operations don't exist for the target
|
|
in the mode requested. The result is not globally atomic, but works so
|
|
long as all parallel references are within #pragma omp atomic directives.
|
|
According to responses received from omp@openmp.org, appears to be within
|
|
spec. Which makes sense, since that's how several other compilers
|
|
handle this situation as well. */
|
|
|
|
static gomp_mutex_t atomic_lock;
|
|
|
|
void
|
|
GOMP_atomic_start (void)
|
|
{
|
|
gomp_mutex_lock (&atomic_lock);
|
|
}
|
|
|
|
void
|
|
GOMP_atomic_end (void)
|
|
{
|
|
gomp_mutex_unlock (&atomic_lock);
|
|
}
|
|
|
|
#if !GOMP_MUTEX_INIT_0
|
|
static void __attribute__((constructor))
|
|
initialize_atomic (void)
|
|
{
|
|
gomp_mutex_init (&atomic_lock);
|
|
}
|
|
#endif
|