From: Bernd Kuhls <bernd@kuhls.net>
To: buildroot@buildroot.org
Subject: [Buildroot] [PATCH 1/1] package/alsa-lib: force -O2 on i386 with gcc >= 15.x
Date: Sat, 11 Jul 2026 13:03:27 +0200 [thread overview]
Message-ID: <20260711110327.862832-1-bernd@kuhls.net> (raw)
Fixes build error on i386:
pcm_dmix_i386.h: In function 'mix_areas_16':
pcm_dmix_i386.h:52:9: error: 'asm' operand has impossible constraints
or there are not enough registers
52 | __asm__ __volatile__ (
Fixes:
https://autobuild.buildroot.net/results/fd9/fd9e6a6f9e2d37df3cfc1ed36707aef9a338f24d/
The oldest build error to be found dates back to Nov 2025:
https://autobuild.buildroot.net/results/3b6/3b606e0c6160563e410535d38a0e7bb09041f223/
so a backport to LTS branches should be considered.
The build error does not occur with gcc 14.4.0 and was reproduced with
gcc 16.1.0.
Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
---
Gitlab pipelines passed:
https://gitlab.com/bkuhls/buildroot/-/commits/d022d480a4556f21d86172a593a92288018ed116
package/alsa-lib/alsa-lib.mk | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/package/alsa-lib/alsa-lib.mk b/package/alsa-lib/alsa-lib.mk
index b6000b3cf3..40dbe0600d 100644
--- a/package/alsa-lib/alsa-lib.mk
+++ b/package/alsa-lib/alsa-lib.mk
@@ -18,6 +18,10 @@ ALSA_LIB_CONF_OPTS = \
--with-pcm-plugins="$(call qstrip,$(BR2_PACKAGE_ALSA_LIB_PCM_PLUGINS))" \
--with-ctl-plugins="$(call qstrip,$(BR2_PACKAGE_ALSA_LIB_CTL_PLUGINS))"
+ifeq ($(BR2_i386)$(BR2_TOOLCHAIN_GCC_AT_LEAST_15),yy)
+ALSA_LIB_CFLAGS += -O2
+endif
+
ifeq ($(BR2_TOOLCHAIN_USES_GLIBC),)
ALSA_LIB_CONF_OPTS += --without-versioned
endif
--
2.47.3
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
reply other threads:[~2026-07-11 11:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260711110327.862832-1-bernd@kuhls.net \
--to=bernd@kuhls.net \
--cc=buildroot@buildroot.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