So, the problem is that TYPE_MAXIMUM (uint_fast8_t) expands to 2**32 - 1, whereas it should expand to 2**64 - 1. Can you use cc -E to find what expression TYPE_MAXIMUM (uint_fast8_t) expands to, and investigate why that expansion evaluates to the wrong value? My impression is that TYPE_MAXIMUM (uint_fast8_t) should expand to (unsigned long) -1, which should be 2**64 - 1 on ia64-hpux11.23, but evidently that is not happening correctly. Perhaps it's a compiler bug?
- verify fails on ia64-hpux11.23 in libunistring-0.9.3 Gary V. Vaughan
- Re: verify fails on ia64-hpux11.23 in libunistring-0.... Gary V. Vaughan
- Re: verify fails on ia64-hpux11.23 in libunistrin... Paul Eggert
- Re: verify fails on ia64-hpux11.23 in libunis... Gary V. Vaughan
- Re: verify fails on ia64-hpux11.23 in lib... Paul Eggert
- Re: verify fails on ia64-hpux11.23 i... Gary V. Vaughan
- Re: verify fails on ia64-hpux11.... Paul Eggert
- Re: verify fails on ia64-hpu... Gary V. Vaughan
- Re: verify fails on ia64-hpu... Paul Eggert
- Re: verify fails on ia64-hpu... Gary V. Vaughan
- Re: verify fails on ia64-hpu... Paul Eggert