diff options
author | Alon Zakai <azakai@google.com> | 2021-04-23 09:17:51 -0700 |
---|---|---|
committer | GitHub <noreply@github.com> | 2021-04-23 09:17:51 -0700 |
commit | 8b66a9d40f55758b99b528d7adb371d275707c5e (patch) | |
tree | 89b53aa2f1a759312200eef6e8638921dbfc0436 /src/passes/OptimizeInstructions.cpp | |
parent | b0dd7fe1b82fa7e3696e06cac1daafd5eb54c221 (diff) | |
download | binaryen-8b66a9d40f55758b99b528d7adb371d275707c5e.tar.gz binaryen-8b66a9d40f55758b99b528d7adb371d275707c5e.tar.bz2 binaryen-8b66a9d40f55758b99b528d7adb371d275707c5e.zip |
Fix a new clang warning on implicit Tuple construction (#3841)
Fixes #3838 and current breakage on CI here.
IIUC the warning is that we define a copy assignment operator, but
did not define a copy constructor. Clang wants both to exist now. However,
we delete the copy assignment one, so perhaps we should find a way to
avoid a copy on construction too? That happens here:
../src/wasm/wasm-type.cpp:60:51: note: in implicit copy constructor for 'wasm::Tuple' first required here
TypeInfo(const Tuple& tuple) : kind(TupleKind), tuple(tuple) {}
^
But I don't see an easy way to remove the copy there, so this PR
defines the copy constructor as clang wants.
Diffstat (limited to 'src/passes/OptimizeInstructions.cpp')
0 files changed, 0 insertions, 0 deletions