Xudong Huang

@zloster Thanks for the info. I just test in the Azure cloud and notice that the wrk server is 100% cpu while the http server is only about 50%.

Thanks! the branch works!

Seems that the i686 target is not well supported. Is it possible to run the test on TARGET="x86_64-pc-windows-msvc"? I will try to fix this for the i686 target.

thanks for reporting. currently this project only supports x64_86 platforms. I don't have ARM based platforms for testing. I hope somebody could help to contribute on other platforms. 😄

the libfringe branch should be an easier porting for ARM, we can just reuse the asm code from [libfringe](https://github.com/edef1c/libfringe). ref #4

ref #4

Could you please supply a corrupted example for the case, so I can do some tests to try. The main usage of the crate is used as a normal static...

I think [ctor](https://crates.io/crates/ctor) may help for the issue, you can just create a dummy generator and then drop it in the shared library before anything running, thus we don't need...

`drop` is just release the resource, it's not important. But create a dummy generator in `ctor` would trigger the initialization in the shared library context.

If you are recursively creating new generator instances, it will consume your heap memory very quickly, but the stack memory is not increasing that too much.