Revision d523b8325857e4cd6f298ec9f356432676c81edb authored by Steven Johnson on 13 March 2021, 00:54:23 UTC, committed by GitHub on 13 March 2021, 00:54:23 UTC
(1) Both the 'deprecated' and new, non-deprecated variants existed back to at least LLVM10, and the deprecated variant was commented as deprecated at that point as well; the change in LLVM13 is that they are now annotated with LLVM_ATTRIBUTE_DEPRECATED so we get compiler warnings (and thus errors). (2) The fixes are simply replicating what the old, deprecated methods did internally.
1 parent c3882a5
AddAtomicMutex.h
#ifndef HALIDE_ADD_ATOMIC_MUTEX_H
#define HALIDE_ADD_ATOMIC_MUTEX_H
#include "Expr.h"
#include <map>
/** \file
* Defines the lowering pass that insert mutex allocation code & locks
* for the atomic nodes that require mutex locks. It also checks whether
* the atomic operation is valid. It rejects algorithms that have indexing
* on left-hand-side which references the buffer itself, e.g.
* f(clamp(f(r), 0, 100)) = f(r) + 1
* If the SplitTuple pass does not lift out the Provide value as a let
* expression. This is confirmed by checking whether the Provide nodes
* inside an Atomic node have let binding values accessing the buffers
* inside the atomic node.
* Finally, it lifts the store indexing expressions inside the atomic node
* outside of the atomic to avoid side-effects inside those expressions
* being evaluated twice. */
namespace Halide {
namespace Internal {
class Function;
Stmt add_atomic_mutex(Stmt s, const std::map<std::string, Function> &env);
} // namespace Internal
} // namespace Halide
#endif
![swh spinner](/static/img/swh-spinner.gif)
Computing file changes ...