From: Guenter Roeck <linux@roeck-us.net>
To: Guo Ren <guoren@kernel.org>
Cc: "Guo Ren" <ren_guo@c-sky.com>, 瞿仙淼 <xianmiao_qu@c-sky.com>,
尚云海 <yunhai_shang@c-sky.com>,
"Guo Ren" <guoren@linux.alibaba.com>,
linux-csky@vger.kernel.org,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] csky: Fixup calltrace panic
Date: Fri, 22 May 2020 14:28:56 -0700 [thread overview]
Message-ID: <15bbf77c-e0cf-59a5-6abc-9eeae93ccc74@roeck-us.net> (raw)
In-Reply-To: <CAJF2gTQj+FzDMM7YNX=iwjpJL3zfuDDua34o+m4pK0rdRYFPwg@mail.gmail.com>
On 5/22/20 8:28 AM, Guo Ren wrote:
> Hi,
>
> On Thu, May 21, 2020 at 10:46 PM Guenter Roeck <linux@roeck-us.net> wrote:
>>> We tested it with https://github.com/c-sky/gcc (gcc-6.3)
>>>
>>
>> That won't work for me. You really might want to consider
>> supporting upstream gcc. I'll try disabling CONFIG_STACKTRACE
>> for csky build tests. If that doesn't work, I may have to
>> disable affected csky build tests for the time being.
>>
>> Guenter
>
> Not only CONFIG_STACKTRACE,
> Disable FRAME_POINTER (Kernel hacking -> Compile the kernel with frame pointers)
>
You are correct. This is what my test builder now does:
Build reference: v5.7-rc6-37-g115a54162a6c
gcc version: csky-linux-gcc (GCC) 9.3.0
Configuration file workarounds:
"s/CONFIG_FRAME_POINTER=y/# CONFIG_FRAME_POINTER is not set/"
Building csky:defconfig ... passed
Building csky:allnoconfig ... passed
Building csky:tinyconfig ... passed
Guenter
prev parent reply other threads:[~2020-05-22 21:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-17 17:52 Guenter Roeck
2020-05-20 7:50 ` Guo Ren
2020-05-21 14:46 ` Guenter Roeck
2020-05-22 15:28 ` Guo Ren
2020-05-22 21:28 ` Guenter Roeck [this message]
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=15bbf77c-e0cf-59a5-6abc-9eeae93ccc74@roeck-us.net \
--to=linux@roeck-us.net \
--cc=guoren@kernel.org \
--cc=guoren@linux.alibaba.com \
--cc=linux-csky@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ren_guo@c-sky.com \
--cc=xianmiao_qu@c-sky.com \
--cc=yunhai_shang@c-sky.com \
/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
all inboxes | Powered by JetHome®