[WASM] Fixed a build error caused by Emscripten version

[akineeic]

Closes #1004

[huningxin]

Thanks @akineeic . Please link this PR to the issue by fix.

Couple of questions:

1. do you know the root cause of this issue?
2. does this patch work for previous emscripten version?

[akineeic]

Thanks @akineeic . Please link this PR to the issue by fix.

Couple of questions:

1. do you know the root cause of this issue?
2. does this patch work for previous emscripten version?

I'm still working on figuring out the cause. I have tested the version 1.38.40 yesterday and it works on that version, the earlier version can be tested if needed.

[huningxin]

@akineeic , any updates on this PR?

[akineeic]

@akineeic , any updates on this PR?

It seems like that the newest version of emscripten doesn't support the writing format of the RuntimeShape's overloading constructor function, but I haven't find the correct way to write it yet.

[akineeic]

I have tested the binding class RuntimeShape in the console, both way to overload the constructor only expose one constructor with one parameter in type of int. In this PR, the emscripten version 1.38.30 is still able to build nn_ops.js and the example using the binding class RuntimeShape is still able to run.

[huningxin]

Thanks for the investigation. As it works for both emscripten, let's merge it while waiting for upstream's response on emscripten-core/emscripten#9704.