This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: proposal to make SIZE_TYPE more flexible
- From: DJ Delorie <dj at redhat dot com>
- To: "Joseph S. Myers" <joseph at codesourcery dot com>
- Cc: gcc at gcc dot gnu dot org
- Date: Wed, 13 Nov 2013 20:58:12 -0500
- 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>
> > So, given all that, is there any way to add the "target-specific
> > size_t" portion without waiting for-who-knows-how-long for the intN_t
> > and enum-size-type projects to finish? Some form of interim API that
> > we can put in, so that we can start working on finding all the
> > assumptions about size_t, while waiting for the rest to finish?
>
> I have no idea how ugly something supporting target-specific strings would
> be, since supporting such strings for these standard typedefs never seemed
> to be a direction we wanted to go in.
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?