On Wed, Oct 18, 2017 at 3:54 PM, Eric Botcazou wrote:
>> Hmm. It makes tracking DIE builds difficult now that not all allocations go
>> through new_die anymore.
>
> I wouldn't have created such a precedent though, IOW there is nothing new.
Ah, didn't notice the other existing cases.
>> Can you
> Hmm. It makes tracking DIE builds difficult now that not all allocations go
> through new_die anymore.
I wouldn't have created such a precedent though, IOW there is nothing new.
> Can you instead split out a new_die_raw
> function with just the allocation and the die_tag initialization? Or ma
On Thu, Oct 12, 2017 at 10:51 PM, Eric Botcazou wrote:
> Hi,
>
> this PR reports a couple of problems with the support of the DW_AT_endianity
> attribute associated with the scalar_storage_order source attribute: it does
> not persist through typedefs and it can contaminate native order DIEs.
>
>
Hi,
this PR reports a couple of problems with the support of the DW_AT_endianity
attribute associated with the scalar_storage_order source attribute: it does
not persist through typedefs and it can contaminate native order DIEs.
The attached patch revamps it by associating native order DIEs and
