From: Dennis Clarke <dclarke@blastwave.org>
To: linux-kernel@vger.kernel.org
Subject: arch/x86/Makefile REALMODE_CFLAGS needs -std=gnu11 with recent GCC versions
Date: Sun, 29 Jun 2025 11:15:13 -0400 [thread overview]
Message-ID: <e4742cae-9ef5-4d30-8c88-65f69e2178cd@blastwave.org> (raw)
Code fix for due to https://bugzilla.kernel.org/show_bug.cgi?id=220294
The summary is that recent GCC versions ( 15.1.0 today ) will assume C23
spec compliance and get upset with ye old A20 address line code bits.
This problem exists previous to the 6.12.35 release tarballs and is
fixed with commit b3bee1e7c3f2b1b77182302c7b2131c804175870 applied.
The newer GCC revisions will be quite popular soon enough and this may
bite people when that happens.
--
--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
Beard and Suspenders installed
next reply other threads:[~2025-06-29 15:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-29 15:15 Dennis Clarke [this message]
2025-06-29 15:33 ` 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=e4742cae-9ef5-4d30-8c88-65f69e2178cd@blastwave.org \
--to=dclarke@blastwave.org \
--cc=linux-kernel@vger.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®