rfc:error-optimizations

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
rfc:error-optimizations [2010/08/25 04:17] – kallerfc:error-optimizations [2017/09/22 13:28] (current) – external edit 127.0.0.1
Line 3: Line 3:
   * Date: 2010-08-21   * Date: 2010-08-21
   * Author: Kalle Sommer Nielsen <kalle@php.net>   * Author: Kalle Sommer Nielsen <kalle@php.net>
-  * Status: In the works+  * Status: Draft (Inactive)
   * First Published at: http://wiki.php.net/rfc/error-optimizations   * First Published at: http://wiki.php.net/rfc/error-optimizations
  
Line 100: Line 100:
  
 Since the error stack is hooked into the executor globals, which requires tsrm_ls to be available in thread safety mode, to avoid a call to TSRMLS_FETCH() everytime we hit the error callbacks or functions (zend_error, zend_error_cb, ...) then we should alter all references to include TSRMLS_DC/TSRMLS_CC for additional performance with ZTS. Since the error stack is hooked into the executor globals, which requires tsrm_ls to be available in thread safety mode, to avoid a call to TSRMLS_FETCH() everytime we hit the error callbacks or functions (zend_error, zend_error_cb, ...) then we should alter all references to include TSRMLS_DC/TSRMLS_CC for additional performance with ZTS.
-  * While altering the internal logic of zend_error() and zend_error_cb() to match that of the above, it might be worth passing the TSRMLS macros to it, to save some TS performance at every call, which itself is a bonus for multithreaded SAPIs. 
rfc/error-optimizations.1282709866.txt.gz · Last modified: 2017/09/22 13:28 (external edit)

Page Tools