| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
| Cc: | thomas(at)pgsql(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Call for platforms |
| Date: | 2001-03-23 08:33:03 |
| Message-ID: | 17485.985336383@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> writes:
>> The bit test diffs seem to indicate that bit_cmp is messed up. That
>> depends on memcmp. I seem to recall something about memcmp not being
>> 8-bit-clean on SunOS ... does that ring a bell with anyone?
> Good point. From the man page of memcmp(3) on this machine:
> BUGS
> memcmp() uses native character comparison, which is signed
> on some machines and unsigned on other machines. Thus the
> sign of the value returned when one of the characters has
> its high-order bit set is implementation-dependent.
Eeek.
The C spec documents I have at hand all agree that memcmp, strcmp,
etc shall interpret their arguments as unsigned char. I hope Sun
were the only ones who took the above more liberal interpretation...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2001-03-23 08:45:28 | Re: Call for platforms |
| Previous Message | Tatsuo Ishii | 2001-03-23 08:19:17 | Re: Call for platforms |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2001-03-23 08:45:28 | Re: Call for platforms |
| Previous Message | Tatsuo Ishii | 2001-03-23 08:19:17 | Re: Call for platforms |