This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [patch 1/4] change specific int128 -> generic intN
- From: DJ Delorie <dj at redhat dot com>
- To: "Joseph S. Myers" <joseph at codesourcery dot com>
- Cc: ebotcazou at adacore dot com, gcc-patches at gcc dot gnu dot org
- Date: Mon, 30 Jun 2014 22:23:09 -0400
- Subject: Re: [patch 1/4] change specific int128 -> generic intN
- Authentication-results: sourceware.org; auth=none
- References: <201404142303 dot s3EN3ONP009938 at greed dot delorie dot com> <Pine dot LNX dot 4 dot 64 dot 1406212014500 dot 29257 at digraph dot polyomino dot org dot uk> <201406242332 dot s5ONWOZn012836 at greed dot delorie dot com> <2471914 dot BhTlkUd4df at polaris> <201406272104 dot s5RL4nKa029229 at greed dot delorie dot com> <Pine dot LNX dot 4 dot 64 dot 1406272131500 dot 8357 at digraph dot polyomino dot org dot uk> <201406272149 dot s5RLnpvn030414 at greed dot delorie dot com> <Pine dot LNX dot 4 dot 64 dot 1406272152410 dot 8357 at digraph dot polyomino dot org dot uk>
> If you find a particular use of TYPE_SIZE is using a size that isn't
> correct for your type whose precision is not a multiple of
> BITS_PER_UNIT, then in my model the correct fix is to change that
> use of TYPE_SIZE rather than to change the value of TYPE_SIZE for
> that type - and such a change (to use TYPE_PRECISION, maybe) would
> also be incremental progress towards eliminating TYPE_SIZE.
What about DECL_SIZE ? It's set from TYPE_SIZE but there is no
DECL_PRECISION.
Also, TYPE_PRECISION is an integer, where TYPE_SIZE is a tree.
They're not universally swappable code-wise.
And I noticed that sizetype and bitsizetype are not really any
different any more either, why have both?