This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
[RFC] HOST_WIDE_INT transition steps
- From: Richard Biener <rguenther at suse dot de>
- To: gcc-patches at gcc dot gnu dot org
- Date: Mon, 19 May 2014 14:43:45 +0200 (CEST)
- Subject: [RFC] HOST_WIDE_INT transition steps
- Authentication-results: sourceware.org; auth=none
The following is my current idea on progressing on the HOST_WIDE_INT
removal
1) https://gcc.gnu.org/ml/gcc-patches/2014-05/msg00381.html (ping)
2) make sure [u]int64_t is available and use that to define HOST_WIDE_INT
3) s/HOST_WIDE_INT/int64_t/ (same for unsigned HOST_WIDE_INT)
Leaves us with HOST_WIDEST_INT (just use [u]int64_t, I don't think
we care for 128bit types). And HOST_WIDEST_FAST_INT for which
I don't have a very good suggestion other than either keeping
it, unconditionally using 'long' (thus simply remove
use_long_long_for_widest_fast_int and handling). The fast_[u]int64_t
types and friends don't seem to be very "useful".
Any comments?
Thanks,
Richard.