This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [RFC] HOST_WIDE_INT transition steps
- From: Richard Biener <rguenther at suse dot de>
- To: Eric Botcazou <ebotcazou at adacore dot com>
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Tue, 20 May 2014 13:23:49 +0200 (CEST)
- Subject: Re: [RFC] HOST_WIDE_INT transition steps
- Authentication-results: sourceware.org; auth=none
- References: <alpine dot LSU dot 2 dot 11 dot 1405191434420 dot 13304 at zhemvz dot fhfr dot qr> <8868910 dot XnRXJS3iKK at polaris> <alpine dot LSU dot 2 dot 11 dot 1405201310260 dot 13304 at zhemvz dot fhfr dot qr> <1768416 dot XG1yqiIQrU at polaris>
On Tue, 20 May 2014, Eric Botcazou wrote:
> > Same as for going C++.
>
> Not to the same extent, this will be worse because done en masse throughout
> the code instead of gradually.
Like the gimple -> gimple * change pending or the various
gimple -> gswitch,glabel,etc. stuff? It's on a similar scale at lest.
> > Make the code base easier to understand for newcomers. It's also a
> > documentation improvement (you see what a HOST_WIDE_INT really is),
> > alongside with [u]int64_t being less to type ...
>
> I personally find the abstraction and the separation with the other, more
> mundane types useful, but I guess that it's a matter of habit.
Yeah. I'm happy of converting only "obvious" cases (or converting
them separately at least). Of course there may be not that many
decoupled pieces ...
Richard.