> On Fri, May 14, 2010 at 9:33 PM, Eric Botcazou wrote:
> >> Ugh. This presents a chicken-and-egg problem to symbol resolution
> >> and type-merging.
> >>
> >> To be clear, the issue is sth like
> >>
> >> unit1
> >> -
> >> int size;
> >> int a[size];
> >>
> >> unit2
> >> --
> >> extern in
On Fri, May 14, 2010 at 9:33 PM, Eric Botcazou wrote:
>> Ugh. This presents a chicken-and-egg problem to symbol resolution
>> and type-merging.
>>
>> To be clear, the issue is sth like
>>
>> unit1
>> -
>> int size;
>> int a[size];
>>
>> unit2
>> --
>> extern int size;
>> extern a[size];
>
> Ugh. This presents a chicken-and-egg problem to symbol resolution
> and type-merging.
>
> To be clear, the issue is sth like
>
> unit1
> -
> int size;
> int a[size];
>
> unit2
> --
> extern int size;
> extern a[size];
>
> ? And you get the a's merged but a diagnostic about mismatched ty
On Fri, May 14, 2010 at 1:24 PM, Eric Botcazou wrote:
> Hi,
>
> most of the remaining warnings issued by the LTO compiler on object files
> compiled from Ada are caused by a small flaw in the GIMPLE types merging
> process: it is done before symbols are merged so compatible types (typically
> doma
Hi,
most of the remaining warnings issued by the LTO compiler on object files
compiled from Ada are caused by a small flaw in the GIMPLE types merging
process: it is done before symbols are merged so compatible types (typically
domain types of arrays) whose distinguishing features depend on sym
