ID:               26797
 Updated by:       [EMAIL PROTECTED]
 Reported By:      yu at fstrf dot org
-Status:           Feedback
+Status:           No Feedback
 Bug Type:         Compile Warning
 Operating System: solaris 8/sparcv9
 PHP Version:      4CVS, 5CVS
 New Comment:

No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Open". Thank you.




Previous Comments:
------------------------------------------------------------------------

[2004-01-19 14:08:54] [EMAIL PROTECTED]

Any news about the patch I provided?


------------------------------------------------------------------------

[2004-01-16 16:32:33] [EMAIL PROTECTED]

Please try this patch:

  http://www.php.net/~jani/patches/bug26797.patch

I don't have ingres available to test myself..so please test if the
compile warnings are gone and the connect funcs still work.

------------------------------------------------------------------------

[2004-01-08 20:45:54] [EMAIL PROTECTED]

SAPI.c warning has been fixed, thanks. 

------------------------------------------------------------------------

[2004-01-05 13:13:06] yu at fstrf dot org

Description:
------------
I met more compiling warnings during the PHP compilation under solaris
8 /sparcv9 64-bit environment besides bug#26769.
____________________________________________________________
1. ingres_ii

warning messages:
=================
php-4.3.4/ext/ingres_ii/ii.c: In function `php_ii_do_connect':
php-4.3.4/ext/ingres_ii/ii.c:602: warning: cast from pointer to integer
of different size
php-4.3.4/ext/ingres_ii/ii.c:604: warning: cast from pointer to integer
of different size
php-4.3.4/ext/ingres_ii/ii.c:605: warning: cast from pointer to integer
of different size
php-4.3.4/ext/ingres_ii/ii.c:607: warning: cast from pointer to integer
of different size

code:
=====
line# 601: link = (II_LINK *) index_ptr->ptr;
line# 602: ptr = zend_list_find((int) link, &type);        /* check if
the link is still there */
line# 603: if (ptr && (type == le_ii_link || type == le_ii_plink)) {
line# 604:      zend_list_addref((int) link);
line# 605:      Z_LVAL_P(return_value) = (int) link;
line# 606: 
line# 607:      php_ii_set_default_link((int) link TSRMLS_CC);
line# 608: 
line# 609:      Z_TYPE_P(return_value) = IS_RESOURCE;
line# 610:        efree(hashed_details);
line# 611:        return;
line# 612: } else {
line# 613:      zend_hash_del(&EG(regular_list), hashed_details,
hashed_details_length + 1);
line# 614: }
____________________________________________________________2. SAPI 

warning messages:
=================
php-4.3.4/main/SAPI.c: In function `sapi_header_op':
php-4.3.4/main/SAPI.c:510: warning: cast from pointer to integer of
different size

code:
=====
line# 509: case SAPI_HEADER_SET_STATUS:
line# 510:      sapi_update_response_code((int) arg TSRMLS_CC);
line# 511:      return SUCCESS;
____________________________________________________________

In the 64-bit environment, pointers are defined in 64-bit. Would these
assignments of 64-bit pointers to a 32-bit integer cause any memory
problems?

Thanks in advance for looking into these.

Maggie




------------------------------------------------------------------------


-- 
Edit this bug report at http://bugs.php.net/?id=26797&edit=1

Reply via email to