tree 9a7cbc46d80e85d1cb08b93d27a51c161b84f34c
parent 885ae7ef3afd88e21c33579bcd64ee3136bd8715
author kshyanashree <109167932+kshyanashree@users.noreply.github.com> 1678730963 -0700
committer GitHub <noreply@github.com> 1678730963 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJkD2bTCRBK7hj4Ov3rIwAAuuUIAHUD9NAxGgpgX1SEdUaB/d6z
 9EpdJNCOv5mz8HQ2k388qobtVxhiwLMZGwvG/aL0+kBPePYfCurfr6ydYXGQC2tk
 Y4KNlVgd3sIipBwZ5tCtcncDKTrGypMwbNJG28nhX4MNKPb3ToJV2ji9jkeZRMmP
 7Dt6rqZ/HGWcjo/ySAK9gDj8FXLvZ7XgDdXOP95XL6hGI6nNmUOklV9PNfpD/o5T
 lst2iH0M++iLR+omsgViNpr+EKpFnf77jlSO7NkP6ViEveg4FNc1BUmYoz3zcxG9
 Ppz++fhpVPL8pBsrPjaUjIa1q+FjYXR2U9HmXwXOrn8Q5fzt1ycnE7ZDk/Y8TwE=
 =0Zfh
 -----END PGP SIGNATURE-----
 

Fix wasm dynamic library extension crash (#17757)

This is an amendment to #17374

We have a C++ toolchain config that's being developed to support standalone wasm. We discovered that #17374 wasn't complete. Our example was poorly written and didn't actually create a wasm dynamic library. These changes allow us to successfully create a standalone wasm dynamic library. Sorry for the botched attempt previously.

I would like to add tests, but I'm unsure how to approach such a tests considering the automatic toolchain doesn't support wasm AFAICT.

Closes #17698.

PiperOrigin-RevId: 516204125
Change-Id: Iced5cc80a3151ffde7116b6264c89eaf40466ff5

Co-authored-by: Ezekiel Warren <zekewarren@gmail.com>