Linux Hexagon architecture development
 help / color / mirror / Atom feed
From: rkuo <rkuo@codeaurora.org>
To: Chen Gang <gang.chen@asianux.com>
Cc: linux-hexagon@vger.kernel.org
Subject: Re: [Suggestion] are they toolchains' issue?
Date: Sat, 9 Nov 2013 18:28:34 -0600	[thread overview]
Message-ID: <20131110002834.GA3879@codeaurora.org> (raw)
In-Reply-To: <527CAF1A.40907@asianux.com>

On Fri, Nov 08, 2013 at 05:30:02PM +0800, Chen Gang wrote:
> Hello Maintainers:
> 
> I met an issue for linux next-20131105
> 
> The related error:
> 
>     CC [M]  fs/ubifs/lpt_commit.o
>   fs/ubifs/lpt_commit.c: In function 'next_pnode_to_dirty':
>   fs/ubifs/lpt_commit.c:620:1: internal compiler error: in hwloop_optimize, at config/hexagon/hexagon.c:5796
>   Please submit a full bug report,
>   with preprocessed source if appropriate.
>   See <http://gcc.gnu.org/bugs.html> for instructions.
> 
> The related information:
> 
>   [root@gchenlinux linux-next]# hexagon-linux-gcc -v
>   Using built-in specs.
>   COLLECT_GCC=hexagon-linux-gcc
>   COLLECT_LTO_WRAPPER=/usr/local/libexec/gcc/hexagon-linux/4.6.1/lto-wrapper
>   Target: hexagon-linux
>   Configured with: ../gcc-hexagon-2012.03/configure --without-header --disable-nls --enable-language=c --disable-threads --disable-shared --enable-werror=no target_configargs=enable_vtable_verify=yes --target=hexagon-linux
>   Thread model: single
>   gcc version 4.6.1 (GCC) 
>   [root@gchenlinux linux-next]# hexagon-linux-ld -v
>   GNU ld (GNU Binutils) 2.21.53.20110905
>   [root@gchenlinux linux-next]# hexagon-linux-as -v
>   GNU assembler version 2.21.53 (hexagon-linux) using BFD version (GNU Binutils) 2.21.53.20110905
> 
> Welcome any suggestions or completions.
> 
> Thanks.
> 

That's definitely a bug; I reproduced it over here as well.  I've submitted 
it to the tools team; I will let you know anything else I find.


Thanks for reporting this!

-Richard Kuo


-- 

Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
hosted by The Linux Foundation

  reply	other threads:[~2013-11-10  0:28 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 ` [Suggestion] are they toolchains' issue? Chen Gang
2013-11-01 19:42   ` 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 [this message]
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=20131110002834.GA3879@codeaurora.org \
    --to=rkuo@codeaurora.org \
    --cc=gang.chen@asianux.com \
    --cc=linux-hexagon@vger.kernel.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