This is an archive of the discontinued LLVM Phabricator instance.

[WebAssembly] Reenable end-to-end test in wasm-eh.cpp
ClosedPublic

Authored by aheejin on May 2 2021, 7:42 PM.

Details

Summary

This was temporarily disabled while we were reimplementing the new spec.

Diff Detail

Event Timeline

aheejin created this revision.May 2 2021, 7:42 PM
aheejin requested review of this revision.May 2 2021, 7:42 PM
Herald added a project: Restricted Project. · View Herald TranscriptMay 2 2021, 7:42 PM
Herald added a subscriber: cfe-commits. · View Herald Transcript
tlively accepted this revision.May 3 2021, 10:31 AM

This is hopefully less controversial because the test already exists and this is just re-enabling it.

This revision is now accepted and ready to land.May 3 2021, 10:31 AM
This revision was automatically updated to reflect the committed changes.

FWIW - please avoid end-to-end tests where possible (writing separate source to LLVM IR (in clang) and LLVM IR to assembly (in LLVM) tests). (recent discussions on the wasm simd instructions touched on this issue too)

@dblaikie I can remove this one. This is not an important test anyway. But where are we supposed to test the arguments clang driver invokes the backend LLVM compilation with? This was mainly to test if -exception-model=wasm reaches the backend compilation.

@dblaikie I can remove this one. This is not an important test anyway. But where are we supposed to test the arguments clang driver invokes the backend LLVM compilation with? This was mainly to test if -exception-model=wasm reaches the backend compilation.

Ah, and that flag is passed down through MCOptions or something like that (something purely in the programmatic API, not serialized into IR)? Fair enough - this is one of the exceptions to the "no end to end testing" rule - if it's the only way to demonstrate that the relevant MCOption was configured correctly, end-to-end testing is the best we've got there.

Thanks for the details!