On Fri, Jul 13, 2012 at 3:59 AM, Mike Stump <mikest...@comcast.net> wrote: > This patch adds __int256 to the front-ends. We follow the __int128 code > fairly closely... > > So, an outstanding question would be, how do I get the mangle codes allocated > for the type? I just choose two unused codes, for now. All in all, the > patch was pretty straight forward. > > We have another patch underway to do N-bit constant ints, where N is defined > by the port. This patch is in the process of being reviewed now, and Kenny > should be able to submit it shortly. > > I tried hard to find all the __int128 bits, but, if there are any I missed, > love to have a pointer to them. > > So, I think we have to resolve which mangle codes to use in some before this > goes in, aside from that, Ok?
How do you handle the fact that we cannot represent all constants of __int256 or larger with an INTEGER_CST? I think this introduces latent wrong-code bugs almost everywhere in the compiler. Richard. > >
