> On 16 May 2025, at 12:10 am, Andi Kleen <a...@firstfloor.org> wrote:
>
> External email: Use caution opening links or attachments
>
>
> On Wed, May 14, 2025 at 02:46:15AM +0000, Kugan Vivekanandarajah wrote:
>> Adding Eugene and Andi to CC as Sam suggested.
>>
>>> On 13 May 2025, at 12:57 am, Richard Sandiford <richard.sandif...@arm.com>
>> wrote:
>>>
>>> External email: Use caution opening links or attachments
>>>
>>>
>>> Kugan Vivekanandarajah <kvivekana...@nvidia.com> writes:
>>>> diff --git a/configure.ac b/configure.ac
>>>> index 730db3c1402..701284e38f2 100644
>>>> --- a/configure.ac
>>>> +++ b/configure.ac
>>>> @@ -621,6 +621,14 @@ case "${target}" in
>>>> ;;
>>>> esac
>>>>
>>>> +autofdo_target="i386"
>>>> +case "${target}" in
>>>> + aarch64-*-*)
>>>> + autofdo_target="aarch64"
>>>> + ;;
>>>> +esac
>>>> +AC_SUBST(autofdo_target)
>>>> +
>>>> # Disable libssp for some systems.
>>>> case "${target}" in
>>>> avr-*-*)
>>>
>>> Couldn't we use the existing $cpu_type, rather than adding a new variable?
>>> I don't think the two would ever need to diverge.
>>
>> I tried doing this but looks to me that $cpu_type is available only in
>> libgcc.
>> Am I missing something or do you want me to replicate that here?
>
> I guess replicating is fine. btw while you are looking at this
> profiledbootstrap is currently disabled for various languages like
> fortran. It would be good to enable it everywhere.
>Thanks. I've updated the patch to utilize cpu_type. While adding support for other languages would be great, I'm currently encountering issues with profile annotation in the autoprofile pass (my other patches and some pending patches). I'll prioritise resolving these annotation problems before adding other language support. However, if anyone else is interested in exploring the additional language support now, please feel free to do so. Is this OK? Thanks, Kugan > Andi
0004-AUTOFDOi_v2-AARCH64-Add-support-for-profilebootstrap.patch
Description: 0004-AUTOFDOi_v2-AARCH64-Add-support-for-profilebootstrap.patch
