This is the mail archive of the
mailing list for the GCC project.
Re: proposal to make SIZE_TYPE more flexible
- From: "Joseph S. Myers" <joseph at codesourcery dot com>
- To: DJ Delorie <dj at redhat dot com>
- Cc: <gcc at gcc dot gnu dot org>
- Date: Thu, 14 Nov 2013 13:26:20 +0000
- Subject: Re: proposal to make SIZE_TYPE more flexible
- Authentication-results: sourceware.org; auth=none
- References: <201310300422 dot r9U4M6Mx002568 at greed dot delorie dot com> <Pine dot LNX dot 4 dot 64 dot 1310301535400 dot 22878 at digraph dot polyomino dot org dot uk> <201310301917 dot r9UJHxg7028662 at greed dot delorie dot com> <Pine dot LNX dot 4 dot 64 dot 1310302035190 dot 29408 at digraph dot polyomino dot org dot uk> <201310302219 dot r9UMJg9e001309 at greed dot delorie dot com> <Pine dot LNX dot 4 dot 64 dot 1310302249250 dot 29408 at digraph dot polyomino dot org dot uk> <201311140158 dot rAE1wCkg006136 at greed dot delorie dot com>
On Wed, 13 Nov 2013, DJ Delorie wrote:
> I tried to hack in support for intN_t in a backend, and it was a maze
> of initialization sequence nightmares. So I guess we need to do the
> intN_t part first. Is someone working on this? If not, is there a
> spec I could use to get started on it?
Instead of a target-independent __int128 keyword, there would be a set
(possibly empty) of __intN keywords, determined by a target hook.
Everything handling __int128 would be updated to work with a
target-determined set of types instead.
Preferably, the number of such keywords would be arbitrary (so I suppose
there would be a single RID_INTN for them) - that seems cleaner than the
system for address space keywords with a fixed block from RID_ADDR_SPACE_0
Joseph S. Myers