public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: ANDY KENNEDY <ANDY.KENNEDY@adtran.com>
To: "'crossgcc@sourceware.org'" <crossgcc@sourceware.org>
Subject: Mips compiler issues.
Date: Thu, 20 Feb 2014 22:46:00 -0000	[thread overview]
Message-ID: <F9C551623D2CBB4C9488801D14F864C68AA76DC1@ex-mb1.corp.adtran.com> (raw)

All,

I know this is not the right list to post this, but here it is anyway.

I'm building a mips toolchain using ct-ng.  Everything builds fine AND
I am able to generate a toolchain that, when statically links, will
produce a viable helloworld on the target (which is an eval board with a
loaded u-Boot, Linux and RFS).  So, I know I'm at least in the right
area.

The problem is when I attempt to build the Linux kernel from within
their SDK.  They have a toolchain in it with the

*multilib_defaults:
-EB mips64r2 mabi=32

which is great, but I don't know what to do in ct-ng to make that
happen.  I have tried all sorts of things but I still cannot make the
Linux kernel build happy.  The Error I get with the latest incantation
is:

  CC      init/main.o
{standard input}: Assembler messages:
{standard input}:395: Error: opcode not supported on this processor: xlr (mips64) `dins $3,$2,0,1'
{standard input}:414: Error: opcode not supported on this processor: xlr (mips64) `di $2'
{standard input}:422: Error: opcode not supported on this processor: xlr (mips64) `di '
{standard input}:422: Error: opcode not supported on this processor: xlr (mips64) `ei '
{standard input}:1304: Error: opcode not supported on this processor: xlr (mips64) `di '
{standard input}:1526: Error: opcode not supported on this processor: xlr (mips64) `di '
{standard input}:1563: Error: opcode not supported on this processor: xlr (mips64) `ei '
{standard input}:1824: Error: opcode not supported on this processor: xlr (mips64) `ei '
{standard input}:2150: Error: opcode not supported on this processor: xlr (mips64) `dins $3,$2,0,1'
{standard input}:2169: Error: opcode not supported on this processor: xlr (mips64) `di $2'
{standard input}:2177: Error: opcode not supported on this processor: xlr (mips64) `di '
{standard input}:2177: Error: opcode not supported on this processor: xlr (mips64) `ei '
make[1]: *** [init/main.o] Error 1

The specs that I have in the ct-ng build toolchain is:

-EB mips1 mabi=n32

If you have any ideas about what I'm doing wrong, please let me know.

In the mean time, I'm still adjusting configurations of ct-ng. . .

Thanks,
Andy

--
For unsubscribe information see http://sourceware.org/lists.html#faq

                 reply	other threads:[~2014-02-20 22:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=F9C551623D2CBB4C9488801D14F864C68AA76DC1@ex-mb1.corp.adtran.com \
    --to=andy.kennedy@adtran.com \
    --cc=crossgcc@sourceware.org \
    /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).