public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Fu, Chao-Ying" <fu@mips.com>
To: Andrew Pinski <pinskia@gmail.com>
Cc: Richard Sandiford <rdsandiford@googlemail.com>,
	       Maxim Kuvyrkov	<maxim@codesourcery.com>,
	       "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: RE: [GCC Steering Committee] Android sub-port reviewer
Date: Tue, 03 Apr 2012 18:28:00 -0000	[thread overview]
Message-ID: <7C6479EB2BF52547AC332FD6034646DA01448C3AEF@exchdb03.mips.com> (raw)
In-Reply-To: <CA+=Sn1nDX8Yf+QE5VO+bQTiRpG25ZO-3PFp4QhkFN=8GEjMaJg@mail.gmail.com>

Andrew Pinski wrote:
> The point is mips*-*-* is big endian and mipsel*-*-* is little endian.
>  And doing adding a target which says mips-linux-android which is
> little-endian is just backwards.  Is there anyway to fix the target
> triplet to be mipsel-linux-android including inside the official NDK?
> If not then we have a broken triplet for android.

  I agree with what you said.

  The simplest fix is that mips-linux-android still generates big-endian code
as the MIPS target triplet design.  Don't ever set it to generate little-endian code automatically.
For MIPS GCC Android patches to merge to FSF GCC trunk, we will never change endiannes.

  Note that we did use a regular mips-linux-gnu GCC to compile Android systems by using -EL.
The target of "mips-linux-android" is just invented to work with NDK scripts.
And people can freely create "mipsel-linux-*" toolchains to compile Android systems directly,
or create "mips-linux-*" toolchains to compile Android systems with -EL.

  The MIPS NDK script patch was just merged to googlesource last night.
I can work on another patch to use -EL options, but to let
"mips-linux-andoird" generate big-endian code.  Is this solution ok for you?

  Thanks!

Regards,
Chao-ying


  reply	other threads:[~2012-04-03 18:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-29  4:39 Maxim Kuvyrkov
2012-04-01 19:57 ` Maxim Kuvyrkov
2012-04-02  9:51   ` Jan Hubicka
2012-04-02 16:38   ` Richard Earnshaw
2012-04-02 18:45   ` Richard Sandiford
2012-04-02 20:55     ` Fu, Chao-Ying
2012-04-03  3:51       ` Andrew Pinski
2012-04-03 17:46         ` Fu, Chao-Ying
2012-04-03 18:08           ` Andrew Pinski
2012-04-03 18:28             ` Fu, Chao-Ying [this message]
2012-04-03 19:21               ` Maxim Kuvyrkov
2012-04-04 22:10                 ` Fu, Chao-Ying

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7C6479EB2BF52547AC332FD6034646DA01448C3AEF@exchdb03.mips.com \
    --to=fu@mips.com \
    --cc=gcc@gcc.gnu.org \
    --cc=maxim@codesourcery.com \
    --cc=pinskia@gmail.com \
    --cc=rdsandiford@googlemail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).