From: Nathan Chancellor <nathan@kernel.org>
To: Miaohe Lin <linmiaohe@huawei.com>
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: Mon, 9 Jan 2023 10:09:15 -0700 [thread overview]
Message-ID: <Y7xKO8IYINf9CcNI@dev-arch.thelio-3990X> (raw)
In-Reply-To: <88dbc59d-1a33-26be-7fd3-0fcdfef33b3a@huawei.com>
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 :)
Cheers,
Nathan
next prev parent reply other threads:[~2023-01-09 17:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-28 12:31 Miaohe Lin
2022-12-28 12:39 ` Borislav Petkov
2022-12-29 1:50 ` Miaohe Lin
2022-12-29 15:17 ` Borislav Petkov
2022-12-30 1:49 ` Miaohe Lin
2022-12-30 11:16 ` Borislav Petkov
2023-01-03 3:05 ` Miaohe Lin
2023-01-05 23:14 ` Borislav Petkov
2023-01-07 2:10 ` Miaohe Lin
2023-01-07 11:07 ` Borislav Petkov
2023-01-09 1:48 ` Miaohe Lin
2023-01-09 11:49 ` Borislav Petkov
2023-01-09 12:32 ` Miaohe Lin
2023-01-09 17:09 ` Nathan Chancellor [this message]
2023-01-10 1:13 ` Miaohe Lin
2022-12-30 12:20 ` Borislav Petkov
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=Y7xKO8IYINf9CcNI@dev-arch.thelio-3990X \
--to=nathan@kernel.org \
--cc=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
all inboxes | Powered by JetHome®