Re: proposed patch to allocsa, vasnprintf for Tandem NSK (OSS)

[Paul Eggert]

Matthew Woehlke <address@hidden> writes:

> Are you not catching the discussion on the coreutils list?

Quite possibly he's not.  To summarize what I have observed so far:

We have observed no bugs when compiling without -O, so that seems to
be a viable platform.

We haven't observed any bug with left shift of long long int, even
with -O.

We have observed some bugs with right shift of long long int with -O;
e.g., (long long int) 0x27a1ad6e467a7e63 >> 1 evaluates to (long long
int) 0x1467a7e63 in some cases.  (I'm guessing about the "1" here; I
don't know the specific value yet.)  We don't yet have a small test
case that illustrates the problem, but I hope Matthew Woehlke can
write and test one for us.  Unfortunately it'll most likely be a
run-time test, but we can arrange for it to be invoked only on hosts
that have long long int but not unsigned long long int, which should
be a pretty small sample.