P: n/a

Hello,
I've rewritten a function (greater_or_equal) that relies on
implementationdefined behavior and availability of exactwidth
integers, with the goal of making the new implementation
(greater_or_equal2) portable across any platform.
What do you think of the new implementation?
(Suggestions and comments are welcome.)
int greater_or_equal(uint16_t u, uint16_t v)
{
return (int16_t)(uv) >= 0;
}
int greater_or_equal2(unsigned u, unsigned v)
{
return ((uv) & 0xffffU) <= 0x7fffU;
}
<OT>
GCC seems to "understand" the source as it outputs the following code.
greater_or_equal2:
movl 8(%esp), %edx
cmpw %dx, 4(%esp)
setns %al
movzbl %al, %eax
ret
</OT>
Regards.  
Share this Question
P: n/a

Noob wrote:
Hello,
I've rewritten a function (greater_or_equal) that relies on
implementationdefined behavior and availability of exactwidth
integers, with the goal of making the new implementation
(greater_or_equal2) portable across any platform.
What do you think of the new implementation?
(Suggestions and comments are welcome.)
int greater_or_equal(uint16_t u, uint16_t v)
{
return (int16_t)(uv) >= 0;
}
int greater_or_equal2(unsigned u, unsigned v)
{
return ((uv) & 0xffffU) <= 0x7fffU;
}
<OT>
GCC seems to "understand" the source as it outputs the following code.
greater_or_equal2:
movl 8(%esp), %edx
cmpw %dx, 4(%esp)
setns %al
movzbl %al, %eax
ret
</OT>
I can't help but wonder, what code does it output for:
int greater_or_equal3(unsigned u, unsigned v)
{
return u >= v;
}
?

pete  
P: n/a

On Apr 28, 10:38*am, Noob <root@localhostwrote:
Hello,
I've rewritten a function (greater_or_equal) that relies on
implementationdefined behavior and availability of exactwidth
integers, with the goal of making the new implementation
(greater_or_equal2) portable across any platform.
What do you think of the new implementation?
(Suggestions and comments are welcome.)
int greater_or_equal(uint16_t u, uint16_t v)
{
* *return (int16_t)(uv) >= 0;
}
int greater_or_equal2(unsigned u, unsigned v)
{
* *return ((uv) & 0xffffU) <= 0x7fffU;
}
<OT>
GCC seems to "understand" the source as it outputs the following code.
greater_or_equal2:
* * *movl * *8(%esp), %edx
* * *cmpw * *%dx, 4(%esp)
* * *setns * %al
* * *movzbl *%al, %eax
* * *ret
</OT>
Regards.
You still use a 2 byte mask, what if unsigned u represents 32 bits?
Suresh M. Shenoy  
P: n/a

On 28 Apr., 19:58, pete <pfil...@mindspring.comwrote:
Noob wrote:
Hello,
I've rewritten a function (greater_or_equal) that relies on
implementationdefined behavior and availability of exactwidth
integers, with the goal of making the new implementation
(greater_or_equal2) portable across any platform.
What do you think of the new implementation?
(Suggestions and comments are welcome.)
int greater_or_equal(uint16_t u, uint16_t v)
{
return (int16_t)(uv) >= 0;
}
int greater_or_equal2(unsigned u, unsigned v)
{
return ((uv) & 0xffffU) <= 0x7fffU;
}
<OT>
GCC seems to "understand" the source as it outputs the following code.
greater_or_equal2:
movl 8(%esp), %edx
cmpw %dx, 4(%esp)
setns %al
movzbl %al, %eax
ret
</OT>
I can't help but wonder, what code does it output for:
int greater_or_equal3(unsigned u, unsigned v)
{
return u >= v;
}
Maybe the code of the OP will be used in a obfuscated
C contest...
Greetings Thomas Mertes
Seed7 Homepage: http://seed7.sourceforge.net
Seed7  The extensible programming language: User defined statements
and operators, abstract data types, templates without special
syntax, OO with interfaces and multiple dispatch, statically typed,
interpreted or compiled, portable, runs under linux/unix/windows.  
P: n/a

Noob wrote:
Hello,
I've rewritten a function (greater_or_equal) that relies on
implementationdefined behavior and availability of exactwidth
integers, with the goal of making the new implementation
(greater_or_equal2) portable across any platform.
What do you think of the new implementation?
(Suggestions and comments are welcome.)
int greater_or_equal(uint16_t u, uint16_t v)
{
return (int16_t)(uv) >= 0;
}
int greater_or_equal2(unsigned u, unsigned v)
{
return ((uv) & 0xffffU) <= 0x7fffU;
}
Neither implementation is correct without an exact definition of what it
does. A function that evaluates greater_or_equal2(60000,0) as 0 would be
surprising to me without a definition to the contrary.

Thad  
P: n/a

Thad Smith wrote:
Noob wrote:
>I've rewritten a function (greater_or_equal) that relies on implementationdefined behavior and availability of exactwidth integers, with the goal of making the new implementation (greater_or_equal2) portable across any platform.
What do you think of the new implementation? (Suggestions and comments are welcome.)
int greater_or_equal(uint16_t u, uint16_t v) { return (int16_t)(uv) >= 0; }
int greater_or_equal2(unsigned u, unsigned v) { return ((uv) & 0xffffU) <= 0x7fffU; }
Neither implementation is correct without an exact definition of what it
does. A function that evaluates greater_or_equal2(60000,0) as 0 would
be surprising to me without a definition to the contrary.
(I agree that I have given these functions unintuitive names, but
I didn't ask whether the two implementations were correct.)
What matters to me is whether the two implementations are equivalent.
That is, given identical input, do they produce identical output?
(The range of legal values for u and v is that of an uint16_t,
i.e. 0 to 65535.)
I should have named the two functions foo1 and foo2, and asked:
"Are foo1 and foo2 equivalent? and is foo2 portable?"
int foo1(uint16_t u, uint16_t v)
{
return (int16_t)(uv) >= 0;
}
int foo2(unsigned u, unsigned v)
{
return ((uv) & 0xffffU) <= 0x7fffU;
}
For those wondering what they're supposed to compute, I provided
more details in an earlier thread.
MessageID: <48**********************@news.free.fr> http://groups.google.com/group/comp....eeb7c981bf2113
For example, 2 is considered "greater than" 65530, because there is
a high probability that 2 is, in fact, 65538 in disguise.
Regards.  
P: n/a

Suresh wrote:
Noob wrote:
>I've rewritten a function (greater_or_equal) that relies on implementationdefined behavior and availability of exactwidth integers, with the goal of making the new implementation (greater_or_equal2) portable across any platform.
What do you think of the new implementation? (Suggestions and comments are welcome.)
int greater_or_equal(uint16_t u, uint16_t v) { return (int16_t)(uv) >= 0; }
int greater_or_equal2(unsigned u, unsigned v) { return ((uv) & 0xffffU) <= 0x7fffU; }
You still use a 2 byte mask,
I think you wrote "byte" where you meant "octet" :)
what if unsigned u represents 32 bits?
I don't understand the question. What did you mean?
The range of legal values for u and v is that of an uint16_t
i.e. 0 to 65535.
Regards.  
P: n/a

pete wrote:
Noob wrote:
>I've rewritten a function (greater_or_equal) that relies on implementationdefined behavior and availability of exactwidth integers, with the goal of making the new implementation (greater_or_equal2) portable across any platform.
What do you think of the new implementation? (Suggestions and comments are welcome.)
int greater_or_equal(uint16_t u, uint16_t v) { return (int16_t)(uv) >= 0; }
int greater_or_equal2(unsigned u, unsigned v) { return ((uv) & 0xffffU) <= 0x7fffU; }
<OT> GCC seems to "understand" the source as it outputs the following code.
greater_or_equal2: movl 8(%esp), %edx cmpw %dx, 4(%esp) setns %al movzbl %al, %eax ret </OT>
I can't help but wonder, what code does it output for:
int greater_or_equal3(unsigned u, unsigned v)
{
return u >= v;
}
Why are you wondering?
greater_or_equal3:
movl 8(%esp), %edx
cmpl %edx, 4(%esp)
setae %al
movzbl %al, %eax
ret
But this is irrelevant, as greater_or_equal3 is /not/ equivalent
to greater_or_equal2. (It doesn't deal with wraparound.)
Consider u=65000 and v=10
greater_or_equal2(65000, 10) returns 0.
greater_or_equal3(65000, 10) returns 1.
Regards.  
P: n/a

Thomas Mertes wrote:
Maybe the code of the OP will be used in a obfuscated C contest...
It is real code, used in a production environment.  
P: n/a

Noob <root@localhostwrites:
<snip>
I should have named the two functions foo1 and foo2, and asked:
"Are foo1 and foo2 equivalent? and is foo2 portable?"
int foo1(uint16_t u, uint16_t v)
{
return (int16_t)(uv) >= 0;
}
int foo2(unsigned u, unsigned v)
{
return ((uv) & 0xffffU) <= 0x7fffU;
}
There is one difference (which I though had already been pointed out,
but I may be missremembering) which is that in foo1, uv may not be
representable as in int16_t, so the conversion is either undefined or,
implementation defined depending on which C standard one is using.

Ben.  
P: n/a

Ben Bacarisse wrote:
Noob wrote:
>I should have named the two functions foo1 and foo2, and asked: "Are foo1 and foo2 equivalent? and is foo2 portable?"
int foo1(uint16_t u, uint16_t v) { return (int16_t)(uv) >= 0; }
int foo2(unsigned u, unsigned v) { return ((uv) & 0xffffU) <= 0x7fffU; }
There is one difference (which I though had already been pointed out,
but I may be missremembering) which is that in foo1, uv may not be
representable as in int16_t, so the conversion is either undefined or,
implementation defined depending on which C standard one is using.
I've already pointed out that foo1 relies on impldefined behavior.
In fact, that is the very reason why I wrote foo2.
The problem statement was:
<quote>
I've rewritten a function that relies on implementationdefined
behavior and availability of exactwidth integers, with the goal
of making the new implementation portable across any platform.
</quote>
On a related subject, I don't think the conversion to int16_t is
ever undefined. (AFAIU, both C89 and C99 say it is impldefined.)
Regards.  
P: n/a

Noob wrote:
Thad Smith wrote:
>Noob wrote:
>>I've rewritten a function (greater_or_equal) that relies on implementationdefined behavior and availability of exactwidth integers, with the goal of making the new implementation (greater_or_equal2) portable across any platform.
What do you think of the new implementation? (Suggestions and comments are welcome.)
int greater_or_equal(uint16_t u, uint16_t v) { return (int16_t)(uv) >= 0; }
int greater_or_equal2(unsigned u, unsigned v) { return ((uv) & 0xffffU) <= 0x7fffU; }
Neither implementation is correct without an exact definition of what it does. A function that evaluates greater_or_equal2(60000,0) as 0 would be surprising to me without a definition to the contrary.
(I agree that I have given these functions unintuitive names, but
I didn't ask whether the two implementations were correct.)
What matters to me is whether the two implementations are equivalent.
That is, given identical input, do they produce identical output?
(The range of legal values for u and v is that of an uint16_t,
i.e. 0 to 65535.)
For the cases that are welldefined by the standard, the results appear
identical. If they give the results you want for the
implementationdefined situations, then you have a good replacement.

Thad  
P: n/a

Noob <root@localhostwrites:
Ben Bacarisse wrote:
>Noob wrote:
>>I should have named the two functions foo1 and foo2, and asked: "Are foo1 and foo2 equivalent? and is foo2 portable?"
int foo1(uint16_t u, uint16_t v) { return (int16_t)(uv) >= 0; }
int foo2(unsigned u, unsigned v) { return ((uv) & 0xffffU) <= 0x7fffU; }
There is one difference (which I though had already been pointed out, but I may be missremembering) which is that in foo1, uv may not be representable as in int16_t, so the conversion is either undefined or, implementation defined depending on which C standard one is using.
I've already pointed out that foo1 relies on impldefined behavior.
In fact, that is the very reason why I wrote foo2.
Ah, right. I thought you were asking a new question.
On a related subject, I don't think the conversion to int16_t is
ever undefined. (AFAIU, both C89 and C99 say it is impldefined.)
Yes, you are right. For some reason, I though the conversion to int
was undefined in C89 (as it is from floating types) but it is indeed
only implementation defined.
To address your question... I'd like to be definitive, but I have no
"calculus" for covering all the possible options. It looks the same,
(assuming one typical behaviour for the implementationdefined cases)
but you know that already. I can't prove it.

Ben.  
P: n/a

On 29 Apr., 11:10, Noob <root@localhostwrote:
pete wrote:
Noob wrote:
I've rewritten a function (greater_or_equal) that relies on
implementationdefined behavior and availability of exactwidth
integers, with the goal of making the new implementation
(greater_or_equal2) portable across any platform.
What do you think of the new implementation?
(Suggestions and comments are welcome.)
int greater_or_equal(uint16_t u, uint16_t v)
{
return (int16_t)(uv) >= 0;
}
int greater_or_equal2(unsigned u, unsigned v)
{
return ((uv) & 0xffffU) <= 0x7fffU;
}
<OT>
GCC seems to "understand" the source as it outputs the following code.
greater_or_equal2:
movl 8(%esp), %edx
cmpw %dx, 4(%esp)
setns %al
movzbl %al, %eax
ret
</OT>
I can't help but wonder, what code does it output for:
int greater_or_equal3(unsigned u, unsigned v)
{
return u >= v;
}
Why are you wondering?
greater_or_equal3:
movl 8(%esp), %edx
cmpl %edx, 4(%esp)
setae %al
movzbl %al, %eax
ret
But this is irrelevant, as greater_or_equal3 is /not/ equivalent
to greater_or_equal2. (It doesn't deal with wraparound.)
Consider u=65000 and v=10
greater_or_equal2(65000, 10) returns 0.
greater_or_equal3(65000, 10) returns 1.
Maybe greater_or_equal3 returns 1 because 65000 is
greater than or equal 10.
Can it be that your function has unsigned parameters,
but you really want to do a signed comparison.
What about something like:
int greater_or_equal4 (unsigned u, unsigned v)
{
return ((int) u) >= ((int) v);
}
that way greater_or_equal4(65000, 10) would return 0
(at least when the size of int and unsigned is 2).
Greetings Thomas Mertes
Seed7 Homepage: http://seed7.sourceforge.net
Seed7  The extensible programming language: User defined statements
and operators, abstract data types, templates without special
syntax, OO with interfaces and multiple dispatch, statically typed,
interpreted or compiled, portable, runs under linux/unix/windows.  
P: n/a

Thomas Mertes wrote:
What about something like:
int greater_or_equal4 (unsigned u, unsigned v)
{
return ((int) u) >= ((int) v);
}
that way greater_or_equal4(65000, 10) would return 0
(at least when the size of int and unsigned is 2).
For the record, the original functions, renamed foo1 and foo2
to prevent people from focusing on their result.
int foo1(uint16_t u, uint16_t v)
{
return (int16_t)(uv) >= 0;
}
int foo2(unsigned u, unsigned v)
{
return ((uv) & 0xffffU) <= 0x7fffU;
}
On my platform, foo1 and foo2 are equivalent.
My claim is that foo2 is portable, while foo1 is not.
greater_or_equal4 is not equivalent to foo2.
(Consider u=32000 and v=33000)
greater_or_equal4 has even worse shortcomings than foo1, as it
requires int and unsigned int to be 16 bits wide, which is not
true on my platform.  
P: n/a

On Wed, 30 Apr 2008 10:49:47 +0200, Noob <root@localhostwrote:
>Thomas Mertes wrote:
>What about something like:
int greater_or_equal4 (unsigned u, unsigned v) { return ((int) u) >= ((int) v); }
that way greater_or_equal4(65000, 10) would return 0 (at least when the size of int and unsigned is 2).
For the record, the original functions, renamed foo1 and foo2 to prevent people from focusing on their result.
int foo1(uint16_t u, uint16_t v) {
return (int16_t)(uv) >= 0;
What happens when u is 0, v is UINT16_MAX, and UINT16_MAX INT16_MAX?
>}
int foo2(unsigned u, unsigned v) {
return ((uv) & 0xffffU) <= 0x7fffU; }
On my platform, foo1 and foo2 are equivalent. My claim is that foo2 is portable, while foo1 is not.
greater_or_equal4 is not equivalent to foo2. (Consider u=32000 and v=33000)
greater_or_equal4 has even worse shortcomings than foo1, as it requires int and unsigned int to be 16 bits wide, which is not true on my platform.
Remove del for email  
P: n/a

Barry Schwarz wrote:
Noob wrote:
>For the record, the original functions, renamed foo1 and foo2 to prevent people from focusing on their result.
int foo1(uint16_t u, uint16_t v) { return (int16_t)(uv) >= 0; }
What happens when u is 0, v is UINT16_MAX, and UINT16_MAX INT16_MAX?
(NB: UINT16_MAX = 65535 and INT16_MAX = 32767)
If u=0 and v=65535 then (int16_t)(uv) evaluates to 1.
And 1 >= 0 evaluates to 1. Therefore foo1 returns 1.
The logic is: If we receive seqno 0 after seqno 65535, then, with high
probability, seqno 0 is, in fact, seqno 65536 in disguise, which is
newer than seqno 65535; which translates to : 0 "is greater than" 65535. http://groups.google.com/group/comp....eeb7c981bf2113
>int foo2(unsigned u, unsigned v) { return ((uv) & 0xffffU) <= 0x7fffU; }
On my platform, foo1 and foo2 are equivalent. My claim is that foo2 is portable, while foo1 is not.
foo2(0, 65535) also returns 1.
Regards.   This discussion thread is closed Replies have been disabled for this discussion.   Question stats  viewed: 973
 replies: 16
 date asked: Jun 27 '08
