Re: Optimizing libc/string for amd64(?)

Matt Emmerton wrote:

>>Wouldn't it be better to set it to "typedef long word"?

> It would probably be better to use int64_t and int32_t instead of long/int,
> in order to make the intention more obvious.

The decision up to the developers. I personally would still use
"long", because it is auto-adjusting and has always the size of
the word on the concerning architecture, AFAIK. I usually try to
avoid ifdefs, whereever it is possible. But there might be already
some other places in the whole codebase where the type for word has
been already computed. It would be even better to use that, because
then it is done just in one place.

But before thinking about a change, it would be better if someone
confirms the degraded performance (just run nbench). I've only checked
it on 1 machine and cannot access it very often (it does not belong
to me).

Martin