[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <15bbf77c-e0cf-59a5-6abc-9eeae93ccc74@roeck-us.net>
Date: Fri, 22 May 2020 14:28:56 -0700
From: Guenter Roeck <linux@...ck-us.net>
To: Guo Ren <guoren@...nel.org>
Cc: Guo Ren <ren_guo@...ky.com>,
瞿仙淼 <xianmiao_qu@...ky.com>,
尚云海 <yunhai_shang@...ky.com>,
Guo Ren <guoren@...ux.alibaba.com>, linux-csky@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] csky: Fixup calltrace panic
On 5/22/20 8:28 AM, Guo Ren wrote:
> Hi,
>
> On Thu, May 21, 2020 at 10:46 PM Guenter Roeck <linux@...ck-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
Powered by blists - more mailing lists