__int256

[Joseph S. Myers]

On Fri, 13 Jul 2012, Georg-Johann Lay wrote:

> The avr port defines __int24 and __uint24.
> Is that compatible with a generic __int24?

In my view, given suitable generic support ports like that should move to 
__intN keywords (usable with "unsigned", so "unsigned __intN" would be the 
unsigned version of that type) and other type names such as __uint24 or 
__uint128_t should be considered deprecated backwards-compatibility 
typedefs (or if necessary macros) provided by the back ends.

It would be good to have a reasonably thorough generic set of testcases 
for the various special-width integer types, used on whichever targets 
support those widths.  If you have a 24-bit type now it might be good to 
extend the floating-point / integer conversion tests I mentioned to cover 
it....

-- 
Joseph S. Myers
joseph@codesourcery.com