* Richard Kenner:
Ada used a 32-bit signed integer type in this case, limiting object size
to 2**31 bits. Is this no longer the case?
It was never the case. You're confusing sizetype with bitsizetype.
The limit was definitely there. Maybe it had a different root cause,
though.
On Mon, May 12, 2008 at 11:58 AM, Mohamed Shafi [EMAIL PROTECTED] wrote:
Hello all,
During debugging in gimple dumps i found a term that is used along
with other data types - bit_size_type.
I am getting ICEs when size of int is 32 bit and no errors when the
size of int is 16. This is
Hello all,
During debugging in gimple dumps i found a term that is used along
with other data types - bit_size_type.
I am getting ICEs when size of int is 32 bit and no errors when the
size of int is 16. This is for a back-end whose native size is 16bit.
Is this any internal data type used to
bitsizetype is a type that can hold any values of sizetype *
BITS_PER_UNIT so we can safely do bit-size calculations without overflow.
This type shouldn't end up used in code though.
Unfortunately, it does, though not in C. Ada's 'Size attribute returns
the size in bits, so the proper type
On Mon, May 12, 2008 at 1:26 PM, Richard Kenner
[EMAIL PROTECTED] wrote:
bitsizetype is a type that can hold any values of sizetype *
BITS_PER_UNIT so we can safely do bit-size calculations without overflow.
This type shouldn't end up used in code though.
Unfortunately, it does, though
I gues you'll get funny effects then, as for Nbit sizetype there's
usually no valid mode for (N+8)bit bitsizetype. In fact, I believe
bitsizetype simply inherits the mode from sizetype.
No. We pick the mode that's *at least* 3 bits wider than sizetype, so
it's usually the next larger integer
On Mon, May 12, 2008 at 6:54 PM, Richard Kenner
[EMAIL PROTECTED] wrote:
I gues you'll get funny effects then, as for Nbit sizetype there's
usually no valid mode for (N+8)bit bitsizetype. In fact, I believe
bitsizetype simply inherits the mode from sizetype.
No. We pick the mode that's *at
On Mon, May 12, 2008 at 3:24 PM, Richard Kenner
[EMAIL PROTECTED] wrote:
I gues you'll get funny effects then, as for Nbit sizetype there's
usually no valid mode for (N+8)bit bitsizetype. In fact, I believe
bitsizetype simply inherits the mode from sizetype.
No. We pick the mode
Yes, but for example when cross-compiling from a 32bit host to a 64bit target
... which is something that's always never worked completey properly ...
On Mon, May 12, 2008 at 12:11:26PM -0400, Richard Kenner wrote:
Yes, but for example when cross-compiling from a 32bit host to a 64bit
target
... which is something that's always never worked completey properly ...
If it doesn't today, then there's no tests covering the problems.
If it doesn't today, then there's no tests covering the problems.
It does if you have a 64-bit HOST_WIDE_INT on your 32-bit host and this is now
enforced for most 64-bit targets.
--
Eric Botcazou
11 matches
Mail list logo
