This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: proposal to make SIZE_TYPE more flexible


> > So where can we begin on all this?
> 
> As noted, make the existing int128 handling more generic (bearing in mind 
> that quite likely much of the language-independent compiler doesn't 
> actually need to know about int128, even if it does at present).

I recall that, but that led to the whole
moving-integer-type-kind-out-of-MI proposal, which led to the
MI-knows-too-much-about-C-types comment.

If I come up with some table-driven API to register
"integer-like-types" and search/sort/choose from them, would that be a
good starting point?  Then we can #define *_type_node to a function
call perhaps.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]