Skip to content

Fix fallback paths in fast_long_{add,sub}_function #17666

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 3 commits into from
Closed
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 10 additions & 4 deletions Zend/zend_operators.h
Original file line number Diff line number Diff line change
Expand Up @@ -49,7 +49,7 @@
#include "zend_multiply.h"
#include "zend_object_handlers.h"

#define LONG_SIGN_MASK ZEND_LONG_MIN
#define LONG_SIGN_MASK (((zend_ulong)1) << (8*sizeof(zend_long)-1))
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The spec is complicated, but I'm not sure this is actually undefined behavior. FWIU, & is well defined for both signed and unsigned integers. In the case of two integers with the same conversion rank, the signed integer will be converted to an unsigned one.

In any case, I find the new and explicit solution a bit more obvious.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The old code (((zend_long)1) << (8*sizeof(zend_long)-1)) (note zend_ulong->zend_long next to the 1) was UB. UBSAN complained at this computation.

Copy link
Member

@iluuu1994 iluuu1994 Feb 2, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The old yes, but the new doesn't. ZEND_LONG_MIN should be equivalent to only the signed bit being set. The only difference between the old and new solution is the signedness, if I understand correctly. Anyway, this looks fine, this wasn't meant as an argument, just trying to understand. 🙂

Edit: I guess ZEND_LONG_MIN is only correct for 2's complement, which is the only binary representation in practice. I'm not sure if this is the only case where we rely on 2's complement, but as mentioned, the new solution is fine too.

Copy link
Member Author

@nielsdos nielsdos Feb 2, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah right, I guess I mixed up ZEND_LONG_MIN with 32/64 bit longs... I'll change that back (to keep the diff as small as possible).

Copy link
Member

@iluuu1994 iluuu1994 Feb 2, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In theory, your new solution is better because it supports all integer representations supported by C. In practice, it likely doesn't matter.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe so. However, we rely on 2s complement in a lot of other places, can you even get a 1s complement system somewhere nowadays?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Absolutely no clue. 🙂

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We could add a respective check to configure.ac.


BEGIN_EXTERN_C()
ZEND_API zend_result ZEND_FASTCALL add_function(zval *result, zval *op1, zval *op2);
Expand Down Expand Up @@ -723,7 +723,7 @@ overflow: ZEND_ATTRIBUTE_COLD_LABEL
*/

if (UNEXPECTED((Z_LVAL_P(op1) & LONG_SIGN_MASK) == (Z_LVAL_P(op2) & LONG_SIGN_MASK)
&& (Z_LVAL_P(op1) & LONG_SIGN_MASK) != ((Z_LVAL_P(op1) + Z_LVAL_P(op2)) & LONG_SIGN_MASK))) {
&& (Z_LVAL_P(op1) & LONG_SIGN_MASK) != (((zend_ulong) Z_LVAL_P(op1) + (zend_ulong) Z_LVAL_P(op2)) & LONG_SIGN_MASK))) {
ZVAL_DOUBLE(result, (double) Z_LVAL_P(op1) + (double) Z_LVAL_P(op2));
} else {
ZVAL_LONG(result, Z_LVAL_P(op1) + Z_LVAL_P(op2));
Expand Down Expand Up @@ -804,11 +804,17 @@ overflow: ZEND_ATTRIBUTE_COLD_LABEL
ZVAL_LONG(result, llresult);
}
#else
ZVAL_LONG(result, Z_LVAL_P(op1) - Z_LVAL_P(op2));
/*
* 'result' may alias with op1 or op2, so we need to
* ensure that 'result' is not updated until after we
* have read the values of op1 and op2.
*/

if (UNEXPECTED((Z_LVAL_P(op1) & LONG_SIGN_MASK) != (Z_LVAL_P(op2) & LONG_SIGN_MASK)
&& (Z_LVAL_P(op1) & LONG_SIGN_MASK) != (Z_LVAL_P(result) & LONG_SIGN_MASK))) {
&& (Z_LVAL_P(op1) & LONG_SIGN_MASK) != (((zend_ulong) Z_LVAL_P(op1) - (zend_ulong) Z_LVAL_P(op2)) & LONG_SIGN_MASK))) {
ZVAL_DOUBLE(result, (double) Z_LVAL_P(op1) - (double) Z_LVAL_P(op2));
} else {
ZVAL_LONG(result, Z_LVAL_P(op1) - Z_LVAL_P(op2));
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess we're not actually testing this branch? Probably would only be used on some pretty esoteric platforms.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess we're not actually testing this branch?

My bad (#17472) ;)

Probably would only be used on some pretty esoteric platforms.

Possibly not even that. Would require a compiler without ASM goto support, no builtins (SADDL etc.) and non Windows system. Plus, that compiler would need to support C11 (or at least the subset we're using).

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's better to perform the integer math once, keeping the result in a temporary variable.
Otherwise C compiler may generate longer fast path code.

}
#endif
}
Expand Down
Loading