On 5/8/2014 3:26 AM, Doug Kwan wrote:
> Add a new user mode target for little-endian PPC64.
>
> Signed-off-by: Doug Kwan <[email protected]>
> ---
> 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)
> + 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"
> + ;;
> sh4|sh4eb)
> TARGET_ARCH=sh4
> bflt="yes"
> diff --git a/default-configs/ppc64el-linux-user.mak
> b/default-configs/ppc64el-linux-user.mak
> new file mode 100644
> index 0000000..6948225
> --- /dev/null
> +++ b/default-configs/ppc64el-linux-user.mak
> @@ -0,0 +1 @@
> +# Default configuration for ppc64el-linux-user
>
We have TCG targets for PowerPC that are bi-endian. It would be much nicer to
have to split
user mode by endianness. If the user loads a BE ELF, then run in BE mode ....
a LE ELF,
then run in LE mode.
I know there is much hand waving in that statement ... but maybe we can do
better? ("we" includes
"me" in that statement ... since I offered to Doug to help out with this).
