Date: Wed, 16 Aug 2017 13:00:16 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 221418] FreeBSD 10.4-PRERELEASE fails to build on systems using 32 bit time_t since r322315. Message-ID: <bug-221418-2472-i3HSStvrpp@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-221418-2472@https.bugs.freebsd.org/bugzilla/> References: <bug-221418-2472@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221418 --- Comment #3 from jau@iki.fi --- To Conrad I have to point out that truncating INT64_MIN to 32 bits might produce INT32_MIN on a big endian system. On a little endian platform the type cast invariably produces a plain zero (0). Concerning my using CHAR_BIT instead of plain numeric 8 I have to say I like portability enough to assume someone some day might wish to use FreeBSD on a system which does not use the 8/16/32/64 bits basic data units division our contemporary systems use. Maybe one day there is a reason to run FreeBSD on a system using 9/18/36 data unit division like in the old PDP-10 or IBM 7094. When there is no real reason to use minimum time_t it is in my opinion really much better to use -(SYNCOOKIE_LIFETIME + 1) as done in the fix 322454. Thanks Michael! --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-221418-2472-i3HSStvrpp>