From: Chen Gang <gang.chen.5i5j@gmail.com>
To: James Hogan <james.hogan@imgtec.com>
Cc: linux-metag@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Suggest] arch: metag: compiler: Are they compiler's issues?
Date: Tue, 24 Dec 2013 11:25:48 +0800 [thread overview]
Message-ID: <52B8FEBC.2070202@gmail.com> (raw)
In-Reply-To: <52B8F33C.3030808@gmail.com>
After by pass these issues and VGA_CONSOLE issue, the metag can pass
allmodconfig for current kernel next tree.
Thanks.
On 12/24/2013 10:36 AM, Chen Gang wrote:
> Helllo Maintainers:
>
> When compile metag with allmodconfig, I met the 2 kinds of issues, I
> guess they are compiler's issues, please help check, thanks.
>
>
> Issue 1: compiler report the issue, but after check the related kernel
> source code, I can not find any issues.
>
> CC [M] drivers/isdn/hisax/s0box.o
> drivers/isdn/hisax/hscx_irq.c: In function 'hscx_fill_fifo':
> /upstream/linux-next/arch/metag/include/asm/io.h:62: error: 'asm' operand requires impossible reload
> make[3]: *** [drivers/isdn/hisax/s0box.o] Error 1
> make[2]: *** [drivers/isdn/hisax] Error 2
> make[1]: *** [drivers/isdn] Error 2
> make: *** [drivers] Error 2
>
>
> Issue 2: they are about structure variables alignment, I guess, the
> compiler can not notice about the "#pragma pack()" correctly.
>
> CC [M] drivers/staging/lustre/lustre/lov/lov_pack.o
> drivers/staging/lustre/lustre/lov/lov_pack.c: In function 'lov_getstripe':
> drivers/staging/lustre/lustre/lov/lov_pack.c:630: error: duplicate case value
> drivers/staging/lustre/lustre/lov/lov_pack.c:630: error: previously used here
> make[5]: *** [drivers/staging/lustre/lustre/lov/lov_pack.o] Error 1
> make[4]: *** [drivers/staging/lustre/lustre/lov] Error 2
> make[3]: *** [drivers/staging/lustre/lustre] Error 2
> make[2]: *** [drivers/staging/lustre] Error 2
> make[1]: *** [drivers/staging] Error 2
> make: *** [drivers] Error 2
>
> MODPOST 2909 modules
> ERROR: "__compiletime_assert_426" [net/batman-adv/batman-adv.ko] undefined!
> ERROR: "__compiletime_assert_429" [net/batman-adv/batman-adv.ko] undefined!
> ERROR: "__compiletime_assert_425" [net/batman-adv/batman-adv.ko] undefined!
> ERROR: "__compiletime_assert_428" [net/batman-adv/batman-adv.ko] undefined!
> ERROR: "__compiletime_assert_427" [net/batman-adv/batman-adv.ko] undefined!
> ERROR: "__compiletime_assert_430" [net/batman-adv/batman-adv.ko] undefined!
>
>
> Making cross-compiler:
>
> git clone git://github.com/img-meta/metag-buildroot.git metag-core-2013.11
> make meta2_defconfig.
> "cd metag-core-2013.11; cp -r output/host/usr/* /usr/"
>
>
> Welcome any additional suggestions, discussions or completions.
>
> Thanks.
>
--
Chen Gang
Open, share and attitude like air, water and life which God blessed
next prev parent reply other threads:[~2013-12-24 3:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-24 2:36 [Suggest] arch: metag: compiler: Are they compiler's issues? Chen Gang
2013-12-24 3:25 ` Chen Gang [this message]
2013-12-24 3:26 ` Chen Gang
2014-01-06 10:31 ` James Hogan
2014-01-08 15:01 ` Chen Gang
2014-01-10 15:57 ` Chen Gang
2014-01-10 16:02 ` James Hogan
2014-01-10 16:20 ` Chen Gang
2014-01-10 16:30 ` James Hogan
2014-01-10 16:38 ` 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=52B8FEBC.2070202@gmail.com \
--to=gang.chen.5i5j@gmail.com \
--cc=james.hogan@imgtec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-metag@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