qemu-ppc
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-ppc] [Qemu-devel] [PATCH 3/3] configure: Add new target ppc64e


From: 關振德
Subject: Re: [Qemu-ppc] [Qemu-devel] [PATCH 3/3] configure: Add new target ppc64el-linux-user
Date: Thu, 8 May 2014 08:57:28 -0700




On Thu, May 8, 2014 at 5:28 AM, Peter Maydell <address@hidden> wrote:
On 8 May 2014 13:18, Andreas Färber <address@hidden> wrote:
> Am 08.05.2014 10:26, schrieb Doug Kwan:
>> Add a new user mode target for little-endian PPC64.
>>
>> Signed-off-by: Doug Kwan <address@hidden>
>> ---
>>  configure                              | 6 ++++++
>>  default-configs/ppc64el-linux-user.mak | 1 +
>>  2 files changed, 7 insertions(+)
>>  create mode 100644 default-configs/ppc64el-linux-user.mak
>>
>> diff --git a/configure b/configure
>> index ac2fa15..ce44044 100755
>> --- a/configure
>> +++ b/configure
>> @@ -4917,6 +4917,12 @@ case "$target_name" in
>>      echo "TARGET_ABI32=y" >> $config_target_mak
>>      gdb_xml_files="power64-core.xml power-fpu.xml power-altivec.xml power-spe.xml"
>>    ;;
>> +  ppc64el)
>
> In SUSE's build system and everywhere I read people talking about it,
> including your 2/3, it's called ppc64le. Why did you choose ppc64el?

In general we should follow what the kernel does, ie
the output of 'uname -m' (which hopefully coincides with
the gcc triplet name). What is that for this case?

thanks
-- PMM

I am aware of the 'le' vs 'el' issue.  However, I saw that all bi-endian targets have 'el' or 'eb' suffixes (e.g. mipsel-linux-user).  So I thought qemu follows the Debian convention.  I will fix that.  

Thanks.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]