qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] [PATCH v2 3/3] Add a new user mode target for little-en


From: 關振德
Subject: Re: [Qemu-devel] [PATCH v2 3/3] Add a new user mode target for little-endian PPC64.
Date: Mon, 12 May 2014 23:45:00 -0700




On Mon, May 12, 2014 at 6:05 AM, Tom Musta <address@hidden> wrote:
On 5/10/2014 4:16 AM, Doug Kwan wrote:
> Signed-off-by: Doug Kwan <address@hidden>
> ---
>  configure                              | 6 ++++++
>  default-configs/ppc64le-linux-user.mak | 1 +
>  2 files changed, 7 insertions(+)
>  create mode 100644 default-configs/ppc64le-linux-user.mak
>
> diff --git a/configure b/configure
> index 46bc0c9..5f0926b 100755
> --- a/configure
> +++ b/configure
> @@ -4912,6 +4912,12 @@ case "$target_name" in
>      TARGET_ABI_DIR=ppc
>      gdb_xml_files="power64-core.xml power-fpu.xml power-altivec.xml power-spe.xml"
>    ;;
> +  ppc64le)
> +    TARGET_ARCH=ppc64
> +    TARGET_BASE_ARCH=ppc
> +    TARGET_ABI_DIR=ppc
> +    gdb_xml_files="power64-core.xml power-fpu.xml power-altivec.xml power-spe.xml"
> +  ;;
>    ppc64abi32)
>      TARGET_ARCH=ppc64
>      TARGET_BASE_ARCH=ppc
> diff --git a/default-configs/ppc64le-linux-user.mak b/default-configs/ppc64le-linux-user.mak
> new file mode 100644
> index 0000000..6948225
> --- /dev/null
> +++ b/default-configs/ppc64le-linux-user.mak
> @@ -0,0 +1 @@
> +# Default configuration for ppc64el-linux-user
>

Now that Alex has taken the decimal floating point into his ppc-next tree, we will also want to
do this, which will trigger building of the decimal floating point library code:

diff --git a/default-configs/ppc64le-linux-user.mak b/default-configs/ppc64le-linux-user.mak
index 6948225..dacbcab 100644
--- a/default-configs/ppc64le-linux-user.mak
+++ b/default-configs/ppc64le-linux-user.mak
@@ -1 +1,2 @@
 # Default configuration for ppc64el-linux-user
+CONFIG_LIBDECNUMBER=y

I will change this (along with the "el" remnant") in V3.


Thank you for taking care of this. 


reply via email to

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