Re: [ZEND-ENGINE-CVS] cvs: ZendEngine2(PHP_5_2) / zend.h zend_API.c zend_builtin_functions.c zend_compile.c zend_execute_API.c zend_object_handlers.c /tests bug43128.phpt php-src NEWS
[email protected] (Stanislav Malyshev)
| Newsgroups | php.zend-engine.cvs |
|---|---|
| Organization | Zend Technologies |
| Message-ID | <[email protected]> |
> We can actually always use malloc in those cases as we weren't using the > checks with alloca in the first place. And on some systems alloca maps > to malloc anyway. On those systems you actually implemented a slowdown. "Some systems" in this case is not any system that is in wide use by PHP users. Linux, Windows, etc all have working alloca. Even if they didn't, it's one if(), which is not really comparable with difference between emalloc() (or, even worse, malloc(), which has locks, etc.) and stack-based alloca(). In 99% of real cases we will be using alloca(), since most of the real class and file names are short. -- Stanislav Malyshev, Zend Software Architect [email protected] http://www.zend.com/ (408)253-8829 MSN: [email protected]