From: Nathan Chancellor <nathan@kernel.org>
To: Aharon Robbins <arnold@skeeve.com>
Cc: linux-kbuild@vger.kernel.org,
Josh Poimboeuf <jpoimboe@kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: Use of `gawk -M' in kernel build scripts
Date: Mon, 5 Oct 2026 10:53:32 +0200 [thread overview]
Message-ID: <20261005085332.GA2094974@ax162> (raw)
In-Reply-To: <E1xDQvK-00000000Kvi-2PZ4@gleep.local>
Hi Aharon,
On Sun, Oct 04, 2026 at 09:26:58PM +0300, Aharon Robbins wrote:
> I'm the maintainer for gawk. I see that it's used in the kernel build
> scripts in combination with objdump.
For the record, the only place where I see '-M' used with gawk is in
scripts/objdump-func, which is not called during the kernel build
thankfully.
> In particular, I note that gawk is invoked with the -M option, which
> uses MPFR for arithmetic (although the precision isn't changed beyond
> the default which is the same as for IEEE hardware floating point).
>
> I am wondering if the -M option is really needed here? The reason I
> ask is that I plan to deprecate MPFR support. The upcoming 6.0 release
> (I hope in Q2 2027) will issue a deprecation warning when -M is used,
> and 6.1 (late 2027 or early 2028, I hope) will have MPFR support removed
> entirely.
>
> So, I wanted to give you folks a heads-up. If -M isn't needed, now's a good
> time to remove its use from the kernel build.
Adding Josh and Peter for the rest of this since they have
added/supported this script.
--
Cheers,
Nathan
next prev parent reply other threads:[~2026-10-05 8:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-04 18:26 Use of `gawk -M' in kernel build scripts Aharon Robbins
2026-10-05 8:53 ` Nathan Chancellor [this message]
2026-10-05 9:02 ` arnold
2026-10-08 7:29 ` arnold
2026-10-13 9:19 ` Peter Zijlstra
2026-10-13 14:41 ` arnold
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=20261005085332.GA2094974@ax162 \
--to=nathan@kernel.org \
--cc=arnold@skeeve.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=peterz@infradead.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