Hi Michael,

The patch seems good to me. I think you can post it on the mailing
list for upstream review at  gcc-patc...@gcc.gnu.org with the AArch64
port maintainers in CC (richard.earns...@arm.com and
marcus.shawcr...@arm.com), and just add the testsuite results of the
lib in your mail, and the ChangeLog entry, something like :

2013-10-02  Michael Hudson-Doyle  <michael.hud...@linaro.org>

        * configure.tgt: Add AArch64 support.

Thanks,
Yvan


On 2 October 2013 03:53, Pinski, Andrew
<andrew.pin...@caviumnetworks.com> wrote:
> This is the same patch which we (Cavium) uses internally if that matters.
>
> Thanks,
> Andrew
>
> Sent from my iPad
>
>> On Oct 1, 2013, at 6:52 PM, "Michael Hudson-Doyle" 
>> <michael.hud...@linaro.org> wrote:
>>
>> ---
>> Hi,
>>
>> Can you review this patch for me and help me get it upstream?
>>
>> This is an official request for help from LEG to the TCWG, if that
>> matters :-)
>>
>> Cheers,
>> mwh
>>
>> libatomic/configure.tgt | 5 -----
>> 1 file changed, 5 deletions(-)
>>
>> diff --git a/libatomic/configure.tgt b/libatomic/configure.tgt
>> index b9e5d6c..7eaab38 100644
>> --- a/libatomic/configure.tgt
>> +++ b/libatomic/configure.tgt
>> @@ -95,11 +95,6 @@ fi
>>
>> # Other system configury
>> case "${target}" in
>> -  aarch64*)
>> -    # This is currently not supported in AArch64.
>> -    UNSUPPORTED=1
>> -    ;;
>> -
>>   arm*-*-linux*)
>>    # OS support for atomic primitives.
>>    config_path="${config_path} linux/arm posix"
>> --
>> 1.8.1.2
>>
>>
>> _______________________________________________
>> linaro-toolchain mailing list
>> linaro-toolchain@lists.linaro.org
>> http://lists.linaro.org/mailman/listinfo/linaro-toolchain
>>
>
> _______________________________________________
> linaro-toolchain mailing list
> linaro-toolchain@lists.linaro.org
> http://lists.linaro.org/mailman/listinfo/linaro-toolchain

_______________________________________________
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain

Reply via email to