Displaying 4 results from an estimated 4 matches for "gvi32_a".
2016 Aug 26
3
Use of array type in globals in LTO
...lobalMerge to handle
>> such cases.
>
> Can you submit a reproduction for Gold please?
> We need to understand what changed with the new LTO API.
I compiled below C code for aarch64 in lto using gold
(--target=aarch64-linux-gnu -flto -fuse-ld=gold). After r278338, two
globals, GVi32_a and GVi32_b, are [4 x i8] type in the input IR to
GlobalMerge. Therefore, GlobalMerge do not even start to handle them
because as of now it ignores fancy-aligned globals. Before r278338,
GVi32_a and GVi32_b seems to be i32 in the input IR to GlobalMerge. Is
this change in the input IR expected...
2016 Aug 26
2
Use of array type in globals in LTO
...ch cases.
>>> Can you submit a reproduction for Gold please?
>>> We need to understand what changed with the new LTO API.
>>
>>
>> I compiled below C code for aarch64 in lto using gold (--target=aarch64-linux-gnu -flto -fuse-ld=gold). After r278338, two globals, GVi32_a and GVi32_b, are [4 x i8] type in the input IR to GlobalMerge. Therefore, GlobalMerge do not even start to handle them because as of now it ignores fancy-aligned globals. Before r278338, GVi32_a and GVi32_b seems to be i32 in the input IR to GlobalMerge. Is this change in the input IR expected ?
&...
2016 Aug 26
2
Use of array type in globals in LTO
...mit a reproduction for Gold please?
>>>>> We need to understand what changed with the new LTO API.
>>>>
>>>>
>>>> I compiled below C code for aarch64 in lto using gold (--target=aarch64-linux-gnu -flto -fuse-ld=gold). After r278338, two globals, GVi32_a and GVi32_b, are [4 x i8] type in the input IR to GlobalMerge. Therefore, GlobalMerge do not even start to handle them because as of now it ignores fancy-aligned globals. Before r278338, GVi32_a and GVi32_b seems to be i32 in the input IR to GlobalMerge. Is this change in the input IR expected ?
&...
2016 Aug 26
2
Use of array type in globals in LTO
On 2016-08-26 11:32, Mehdi Amini wrote:
> Hi,
>
>> Recently, I noticed that less number of global variables are merged in
>> global-merge pass and in some global variable, array types are used
>> instead of its original type. For example, [4xi8] with align 4 is used
>> for a i32 global variable. For me, it seems that such pattern is
>> observed after