This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH][2/n] Always 64bit-HWI cleanups
- From: Richard Sandiford <rdsandiford at googlemail dot com>
- To: Richard Biener <rguenther at suse dot de>
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Wed, 28 May 2014 22:47:46 +0100
- Subject: Re: [PATCH][2/n] Always 64bit-HWI cleanups
- Authentication-results: sourceware.org; auth=none
- References: <alpine dot LSU dot 2 dot 11 dot 1405231333180 dot 2632 at zhemvz dot fhfr dot qr>
Richard Biener <rguenther@suse.de> writes:
> The following changes the configury to insist on [u]int64_t being
> available and removes the very old __int64 case. Autoconf doesn't
> check for it, support came in via a big merge in Dec 2002, r60174,
> and it was never used on the libcpp side until I fixed that with
> the last patch of this series, so we couldn't have relied on it
> at least since libcpp was introduced.
>
> Both libcpp and vmsdbg.h now use [u]int64_t, switching HOST_WIDE_INT
> to literally use int64_t has to be done with the grand renaming of
> all users due to us using 'unsigned HOST_WIDE_INT'.
>
> Btw, I couldn't find any "standard" way of writing
> [u]int64_t literals (substitution for HOST_WIDE_INT_C) nor
> one for printf formats (substitutions for HOST_WIDE_INT_PRINT
> and friends). I'll consider doing s/HOST_WIDE_INT/[U]INT64/
> there if nobody comes up with a better plan.
Not sure whether you meant that to apply to both groups, but as far as
the HOST_WIDE_INT_C replacement goes, how about just using int64_t (N)
instead of HOST_WIDE_INT_C (N) or INT64_C (N)?
Thanks,
Richard