From: Chen Gang <gang.chen@asianux.com>
To: Chris Metcalf <cmetcalf@tilera.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Suggestion] tile: include: asm: missing "feedback.h" file.
Date: Fri, 28 Jun 2013 08:28:01 +0800 [thread overview]
Message-ID: <51CCD891.8000806@asianux.com> (raw)
In-Reply-To: <51CC492C.1040105@tilera.com>
On 06/27/2013 10:16 PM, Chris Metcalf wrote:
> On 6/26/2013 12:25 AM, Chen Gang wrote:
>> > Hello Maintainers:
>> >
>> > The compilation failed by "make ARCH=tile tilegx_defconfig", and "make
>> > ARCH=tile CROSS_COMPILE=tile-linux-gnu-" for upstream next-20130625.
>> >
>> > The related error:
>> >
>> > CC kernel/bounds.s
>> > In file included from include/linux/linkage.h:7:0,
>> > from include/linux/kernel.h:6,
>> > from include/asm-generic/bug.h:13,
>> > from arch/tile/include/generated/asm/bug.h:1,
>> > from include/linux/bug.h:4,
>> > from include/linux/page-flags.h:9,
>> > from kernel/bounds.c:9:
>> > /root/linux-next/arch/tile/include/asm/linkage.h:18:22: fatal error: feedback.h: No such file or directory
>> >
>> > We really need "feedback.h"
>> >
>> > arch/tile/kernel/entry.S: Assembler messages:
>> > arch/tile/kernel/entry.S:26: Error: Unknown opcode `feedback_enter(current_text_addr)'.
>> > arch/tile/kernel/entry.S:46: Error: Unknown opcode `feedback_enter(dump_stack)'.
>> > arch/tile/kernel/entry.S:53: Error: Unknown opcode `feedback_enter(KBacktraceIterator_init_current)'.
>> > arch/tile/kernel/entry.S:61: Error: Unknown opcode `feedback_enter(smp_nap)'.
>> > arch/tile/kernel/entry.S:76: Error: Unknown opcode `feedback_enter(_cpu_idle)'.
>> >
>> > Welcome any suggestions and completions.
> This is fixed in gcc 4.7.2 or later. For the workaround, see:
>
> http://www.tilera.com/scm/source.html#feedback_h
>
Thank you very much.
> Essentially, you just have to create a dummy <feedback.h> header, e.g. for 4.7.1:
>
> cat > $install/lib/gcc/tilegx-unknown-linux-gnu/4.7.1/include/feedback.h
> #define FEEDBACK_ENTER_EXPLICIT(FUNCNAME, SECNAME, SIZE)
> #define FEEDBACK_ENTER(FUNCNAME)
> #define FEEDBACK_REENTER(FUNCNAME)
> #define FEEDBACK_ENTRY(FUNCNAME, SECNAME, SIZE)
> ^D
I should try as soon as possible.
Thanks again.
--
Chen Gang
next prev parent reply other threads:[~2013-06-28 0:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-26 4:25 Chen Gang
2013-06-27 14:16 ` Chris Metcalf
2013-06-28 0:28 ` Chen Gang [this message]
2013-06-28 1:51 ` [PATCH] arch: tile: include: asm: add cmpxchg64() definition Chen Gang
2013-06-28 15:09 ` Ralf Baechle
2013-07-01 2:08 ` Chen Gang
2013-07-01 2:21 ` [PATCH v2] " Chen Gang
2013-07-17 16:46 ` Chris Metcalf
2013-07-18 0:02 ` 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=51CCD891.8000806@asianux.com \
--to=gang.chen@asianux.com \
--cc=cmetcalf@tilera.com \
--cc=linux-kernel@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
Powered by JetHome