From: Borislav Petkov <bp@alien8.de>
To: Miaohe Lin <linmiaohe@huawei.com>
Cc: "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: Mon, 9 Jan 2023 12:49:57 +0100 [thread overview]
Message-ID: <Y7v/ZVTeQCw7Hv8g@zn.tnic> (raw)
In-Reply-To: <08115444-73a3-b9b0-dbeb-2a0cf374290e@huawei.com>
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.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next parent reply other threads:[~2023-01-09 11:51 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 ` Borislav Petkov [this message]
2023-01-09 12:32 ` [BUG Report] undefined reference to `convert_to_fxsr' Miaohe Lin
2023-01-09 17:09 ` Nathan Chancellor
2023-01-10 1:13 ` Miaohe Lin
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=Y7v/ZVTeQCw7Hv8g@zn.tnic \
--to=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-toolchains@vger.kernel.org \
--cc=matz@suse.de \
--cc=mingo@redhat.com \
--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).