From: Miaohe Lin <linmiaohe@huawei.com>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Borislav Petkov <bp@alien8.de>, "x86@kernel.org" <x86@kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>, <hpa@zytor.com>,
linux-toolchains ML <linux-toolchains@vger.kernel.org>,
Michael Matz <matz@suse.de>
Subject: Re: [BUG Report] undefined reference to `convert_to_fxsr'
Date: Tue, 10 Jan 2023 09:13:53 +0800 [thread overview]
Message-ID: <f2b54d81-f950-0e6f-5772-dcbdffa6974e@huawei.com> (raw)
In-Reply-To: <Y7xKO8IYINf9CcNI@dev-arch.thelio-3990X>
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
prev parent reply other threads:[~2023-01-10 1:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Y6w49Y1d3lpv3KFn@zn.tnic>
[not found] ` <23e2907c-5188-5ac6-3db8-1c5a12120bf2@huawei.com>
[not found] ` <Y62vbjBzHF4rmh1V@zn.tnic>
[not found] ` <e041533c-4005-b9bc-3985-02224985aa28@huawei.com>
[not found] ` <Y67IlthBqaX69RwN@zn.tnic>
[not found] ` <64fe1be4-954f-fe6f-44f0-59b572548663@huawei.com>
[not found] ` <Y7dZwWsiUfHKxN3S@zn.tnic>
[not found] ` <d312c572-f232-a4e9-2ecc-023050528a29@huawei.com>
[not found] ` <Y7lSZerjPghqllWp@zn.tnic>
[not found] ` <08115444-73a3-b9b0-dbeb-2a0cf374290e@huawei.com>
2023-01-09 11:49 ` [BUG Report] undefined reference to `convert_to_fxsr' Borislav Petkov
2023-01-09 12:32 ` Miaohe Lin
2023-01-09 17:09 ` Nathan Chancellor
2023-01-10 1:13 ` Miaohe Lin [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=f2b54d81-f950-0e6f-5772-dcbdffa6974e@huawei.com \
--to=linmiaohe@huawei.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-toolchains@vger.kernel.org \
--cc=matz@suse.de \
--cc=mingo@redhat.com \
--cc=nathan@kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).