On 22/08/2017 11:57, Jozef Lawrynowicz wrote:
On 02/08/2017 17:45, Joseph Myers wrote:
On Wed, 2 Aug 2017, Jeff Law wrote:
I think Joseph's suggestion for looking at partial float handling may be
useful, though ia64's RFmode may be more interesting as it's not a
multiple of 8 in bitsize.
On 02/08/2017 17:45, Joseph Myers wrote:
On Wed, 2 Aug 2017, Jeff Law wrote:
I think Joseph's suggestion for looking at partial float handling may be
useful, though ia64's RFmode may be more interesting as it's not a
multiple of 8 in bitsize. IF/KF modes on the ppc port have similar
On Wed, 2 Aug 2017, Jeff Law wrote:
> I think Joseph's suggestion for looking at partial float handling may be
> useful, though ia64's RFmode may be more interesting as it's not a
> multiple of 8 in bitsize. IF/KF modes on the ppc port have similar
> properties.
The key issue those
On 08/01/2017 10:26 AM, Jozef Lawrynowicz wrote:
> On 01/08/2017 00:08, Joseph Myers wrote:
>> On Wed, 26 Jul 2017, Jeff Law wrote:
>>
>>> TYPE_SIZE, according to my understanding, should be a tree for the size
>>> of the expression in bits.
>>>
>>> The problem is for msp430 that size varies
On 07/31/2017 05:08 PM, Joseph Myers wrote:
> On Wed, 26 Jul 2017, Jeff Law wrote:
>
>> TYPE_SIZE, according to my understanding, should be a tree for the size
>> of the expression in bits.
>>
>> The problem is for msp430 that size varies depending on where it's used.
>> ie, in a register an
On 01/08/2017 00:08, Joseph Myers wrote:
On Wed, 26 Jul 2017, Jeff Law wrote:
TYPE_SIZE, according to my understanding, should be a tree for the size
of the expression in bits.
The problem is for msp430 that size varies depending on where it's used.
ie, in a register an object might have a
On Wed, 26 Jul 2017, Jeff Law wrote:
> TYPE_SIZE, according to my understanding, should be a tree for the size
> of the expression in bits.
>
> The problem is for msp430 that size varies depending on where it's used.
> ie, in a register an object might have a bitsize of 20 bits, but in
> memory
On 05/19/2017 07:35 AM, Jozef Lawrynowicz wrote:
> Original post: https://gcc.gnu.org/ml/gcc-patches/2017-04/msg01030.html
>
> The attached patch fixes an issue for the msp430 target where the TYPE_SIZE of
> the __int20 type was set using the precision (20 bits) instead of the
> in-memory
> size
Original post: https://gcc.gnu.org/ml/gcc-patches/2017-04/msg01030.html
The attached patch fixes an issue for the msp430 target where the TYPE_SIZE of
the __int20 type was set using the precision (20 bits) instead of the in-memory
size (32 bits) of the type. This bug caused an ICE as reported in
