To all internals, but especially to Zeev and Dmitry, Having a JIT which does not support ZTS is a bit short-sighted. Think about it. You want to add a JIT partly so that PHP will be better at non-web, CPU intensive tasks. If the JIT is successful, eventually you will want parallelism in that domain, and if you are going to use threading then something like ZTS is required.
Additionally, a lot of people are using ZTS builds today. You can argue all you want, we can't remove it easily. Imagine if I proposed a breaking change in the language that would affect these same users. Unless we got a *lot* of value out of it, I don't think it would pass. And no offense, but in its current state the JIT does not have a lot of value. It's a promising prototype, but it's not going to help the vast majority of our users. So, respectfully, I hope we can quit talking about removing ZTS. It is required for the present, and it will probably be desirable in the future. Therefore, *some* mechanism for a thread-safe JIT code generation is a requirement. It doesn't necessarily have to be the ZTS we have today, but it needs something. Regards, Levi Morrison -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
