Revision 1dbcf198f22f1b541f61a1a64f02fc8e9656755a authored by Steven Johnson on 21 December 2020, 17:08:20 UTC, committed by GitHub on 21 December 2020, 17:08:20 UTC
* Decouple wasm's +bulk-memory from threads When `wasm_threads` was added, `+bulk-memory` codegen was enabled in conjunction with this feature, due to some inscrutable error which apparently didn't get recorded. From inspection of the spec for bulk-memory, and experimentation with the most recent version of Emscripten (2.0.10), I can't find any reason that this actually needs to be enabled, so I've moved it into its own new feature flag. Also: drive-by fix in Target to format the tables in `get_runtime_compatible_target()` better, and to remove some wasm-related entries from the 'must match' table that didn't actually need to match. * Create .gitignore
1 parent ef45c87
DebugToFile.h
#ifndef HALIDE_DEBUG_TO_FILE_H
#define HALIDE_DEBUG_TO_FILE_H
/** \file
* Defines the lowering pass that injects code at the end of
* every realization to dump functions to a file for debugging. */
#include <map>
#include <vector>
#include "Expr.h"
namespace Halide {
namespace Internal {
class Function;
/** Takes a statement with Realize nodes still unlowered. If the
* corresponding functions have a debug_file set, then inject code
* that will dump the contents of those functions to a file after the
* realization. */
Stmt debug_to_file(Stmt s,
const std::vector<Function> &outputs,
const std::map<std::string, Function> &env);
} // namespace Internal
} // namespace Halide
#endif
Computing file changes ...
