Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [day] [month] [year] [list]
Message-Id: <043F4738-3303-496F-88B7-7252AFEB2D7C@gmail.com>
Date: Fri, 21 Aug 2015 18:16:41 +0800
From: Lei Zhang <zhanglei.april@...il.com>
To: john-dev@...ts.openwall.com
Subject: Question about type ARCH_WORD_32/64

Hi,

I just got a "incompatible pointer type" warning when casting a (uint64_t*) pointer to an (ARCH_WORD_64*) pointer on Power. This happens because ARCH_WORD_64 is defined as 'unsigned long long', while uint64_t is define as 'unsigned long' on Power. They're supposed to be the exactly same type on this arch, but somehow gcc disagrees.

OTOH, why invent ARCH_WORD_32/64 when uint32_t/uint64_t is at hand? Is there any portability problem with uint32_t/uint64_t? Or is ARCH_WORD_32/64 some legacy stuff?


Lei

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.