[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <f2b54d81-f950-0e6f-5772-dcbdffa6974e@huawei.com>
Date: Tue, 10 Jan 2023 09:13:53 +0800
From: Miaohe Lin <linmiaohe@...wei.com>
To: Nathan Chancellor <nathan@...nel.org>
CC: Borislav Petkov <bp@...en8.de>, "x86@...nel.org" <x86@...nel.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"mingo@...hat.com" <mingo@...hat.com>,
Dave Hansen <dave.hansen@...ux.intel.com>, <hpa@...or.com>,
linux-toolchains ML <linux-toolchains@...r.kernel.org>,
Michael Matz <matz@...e.de>
Subject: Re: [BUG Report] undefined reference to `convert_to_fxsr'
On 2023/1/10 1:09, Nathan Chancellor wrote:
> On Mon, Jan 09, 2023 at 08:32:09PM +0800, Miaohe Lin wrote:
>> On 2023/1/9 19:49, Borislav Petkov wrote:
>>> On Mon, Jan 09, 2023 at 09:48:50AM +0800, Miaohe Lin wrote:
>>>> Oh, sorry, I miss-read that. My compiler is gcc-7.3.0 which contains many
>>>> in-house codes from our company in it. That might matters. Thanks a lot for
>>>> your guidance. :)
>>>
>>> Yah, next time, before you report something like that, try to reproduce it with
>>> an official compiler (gcc from the upstream repo, SUSE, Debian, RH-built etc).
>>>
>>> If it doesn't reproduce, go complain to the folks who hack your in-house
>>> compiler.
>>
>> Sorry, my bad! I thought my compiler is just as same as upstream one... Many thanks for your time.
>
> Just for the future, in case you were not aware of it, Arnd provides
> vanilla GCC toolchains, which can be really helpful for ruling out
> (or blaming) downstream compiler patches as the cause of problems:
>
> https://mirrors.edge.kernel.org/pub/tools/crosstool/
>
> You might not run into this problem again but if you do, it might save
> some time :)
That's really helpful! Many thanks for your offer. :)
Thanks,
Miaohe Lin
Powered by blists - more mailing lists