From: Willy Tarreau <w@1wt.eu>
To: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
Cc: ast@kernel.org, yhs@fb.com, sean.wang@mediatek.com,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>
Subject: Re: Unable bisect issue because kernel not building from old commits
Date: Sun, 25 Sep 2022 06:20:31 +0200 [thread overview]
Message-ID: <20220925042031.GA9845@1wt.eu> (raw)
In-Reply-To: <CABXGCsN8LHqz7=OSvBpKCqKdV4L_4FPXtQ32bgYveA9yP2_xiQ@mail.gmail.com>
On Sun, Sep 25, 2022 at 03:22:10AM +0500, Mikhail Gavrilov wrote:
> Hi!
> I want to make bisect between commits fdaf9a5840ac and babf0bb978e3,
> because after commit babf0bb978e3 Wi-Fi (mt7921e) upload speed became
> limited to 170Mbps. On commit fdaf9a5840ac upload speed was 784Mbps.
>
> But I ran into a problem that the gcc-12.2.1 compiler on my
> distribution (Fedora) can't build the kernel from old commits. The
> build fails with the following error:
> ld: warning: arch/x86/power/hibernate_asm_64.o: missing
> .note.GNU-stack section implies executable stack
(...)
Note that this looks more related to binutils here. Regardless, there
are pre-built toolchains including compiler+binutils for various gcc
versions from 4.9 and up here, for all supported architectures:
https://mirrors.edge.kernel.org/pub/tools/crosstool/
These ones are sufficient to build a kernel and are likely easier to
deal with than trying to port a patch over a bisect session. For example
you could have luck with 7.5 which has been supported for a very long
time and still is supported.
Hoping this helps,
Willy
next prev parent reply other threads:[~2022-09-25 4:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-24 22:22 Unable bisect issue because kernel not building from old commits Mikhail Gavrilov
2022-09-25 4:20 ` Willy Tarreau [this message]
2022-09-25 14:02 ` Mikhail Gavrilov
2022-09-25 15:21 ` Willy Tarreau
2022-09-25 16:13 ` Mikhail Gavrilov
2022-09-25 18:43 ` Willy Tarreau
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=20220925042031.GA9845@1wt.eu \
--to=w@1wt.eu \
--cc=ast@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikhail.v.gavrilov@gmail.com \
--cc=sean.wang@mediatek.com \
--cc=yhs@fb.com \
/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