You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am calling wasm-merge, wasm-metadce, and wasm-opt in sequence and the output of the first two steps both errors with "Some VMs may not accept this binary because it has a large number of locals in function". I think it makes sense to silence this error with some flag that implies that the result isn't final or that there are further optimizations that will be applied.
I'm not confident if this is the only type of error that it makes sense to do something like this and how special-cased the solution might be.
The text was updated successfully, but these errors were encountered:
Does the --quiet flag not help there? If not then maybe we should make it apply to that. Another option might be -w to silence all warnings, perhaps, which I don't think we have yet. (I'm not sure which option is best.)
std::cerr << "Some VMs may not accept this binary because it has a large "
I think either that or -w would be an improvement but maybe not ideal. My hesitancy with recommending either of those directly was around how this does feel like a context-dependent hard error. As a final artifact, this wasm file would be unusable and so in that context a --quiet silencing the error report would be a shame.
I am calling
wasm-merge
,wasm-metadce
, andwasm-opt
in sequence and the output of the first two steps both errors with "Some VMs may not accept this binary because it has a large number of locals in function". I think it makes sense to silence this error with some flag that implies that the result isn't final or that there are further optimizations that will be applied.I'm not confident if this is the only type of error that it makes sense to do something like this and how special-cased the solution might be.
The text was updated successfully, but these errors were encountered: