Linux Hexagon architecture development
 help / color / mirror / Atom feed
From: Chen Gang <gang.chen@asianux.com>
To: Richard Kuo <rkuo@codeaurora.org>
Cc: linux-hexagon@vger.kernel.org
Subject: [Suggestion] are they toolchains' issue?
Date: Fri, 01 Nov 2013 20:05:52 +0800	[thread overview]
Message-ID: <52739920.4010905@asianux.com> (raw)
In-Reply-To: <527396BA.7050906@asianux.com>

Hello Maintainers:

When compiling with allmodconfig for v4, an error occurs:

    CC      kernel/fork.o
  /tmp/ccTx69dj.s: Assembler messages:
  /tmp/ccTx69dj.s:7853: Error: invalid instruction `if (tstbit(r4.new,r0))jump:nt .L242'

Also when with allmodconfig (default for v2), it will cause error:

  /usr/local/bin/hexagon-ld: Relocatable linking with relocations from format elf32-littlehexagon (init/.tmp_main.o) to format elf32-littlehexagon (init/main.o) is not supported

Also when with defconfig, it will cause error:

    LD      init/mounts.o
  /usr/local/bin/hexagon-ld: Relocatable linking with relocations from format elf32-littlehexagon (init/do_mounts.o) to format elf32-littlehexagon (init/mounts.o) is not supported


Toolchain Information:

  https://www.codeaurora.org/patches/quic/hexagon/dev/
  gcc-4.4_full_111104.bz2 and gnutools_full_111104.bz2
  
  [root@gchenlinux hexagon]# hexagon-gcc -v
  Using built-in specs.
  Target: hexagon
  Configured with: ../gcc-4.4/configure --without-header --disable-nls --enable-language=c --disable-threads --disable-shared --enable-werror=no target_configargs=enable_vtable_verify=yes --target=hexagon
  Thread model: single
  gcc version 4.4.0 : Hexagon Build Version (UNKNOWN) UNKNOWN (GCC) 
  [root@gchenlinux hexagon]# hexagon-ld -v
  GNU ld (GNU Binutils) 2.20 20091016
  Hexagon Build Version X.Y.ZZ XXXXXXXXXXX_YYYY_ZZZZZ
  [root@gchenlinux hexagon]# hexagon-as -v
  GNU assembler version 2.20 (hexagon) using BFD version (GNU Binutils) 2.20 20091016
  Hexagon Build Version X.Y.ZZ XXXXXXXXXXX_YYYY_ZZZZZ


Please help check, and welcome any suggestions or completions.


Thanks.
--
Chen Gang.

  reply	other threads:[~2013-11-01 12:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-01 11:55 [PATCH] hexagon: include: asm: kgdb: extend DBG_MAX_REG_NUM for "cs0/1" Chen Gang
2013-11-01 12:05 ` Chen Gang [this message]
2013-11-01 19:42   ` [Suggestion] are they toolchains' issue? rkuo
2013-11-02 13:29     ` Chen Gang
2013-11-06  2:56       ` Chen Gang
2013-11-08  9:30         ` Chen Gang
2013-11-10  0:28           ` rkuo
2013-11-10  0:38             ` Chen Gang
2013-11-01 17:14 ` [PATCH] hexagon: include: asm: kgdb: extend DBG_MAX_REG_NUM for "cs0/1" Linas Vepstas
2013-11-02 13:19   ` Chen Gang

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=52739920.4010905@asianux.com \
    --to=gang.chen@asianux.com \
    --cc=linux-hexagon@vger.kernel.org \
    --cc=rkuo@codeaurora.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