All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/alsa-lib: force -O2 on i386 with gcc >= 15.x
Date: Sun, 16 Aug 2026 17:08:08 +0200	[thread overview]
Message-ID: <aoHSI9MWvRFbPAWO@windsurf> (raw)
In-Reply-To: <20260711110327.862832-1-bernd@kuhls.net>

On Sat, Jul 11, 2026 at 01:03:27PM +0200, Bernd Kuhls wrote:
> 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.

I have no doubt that passing -O2 works around the issue, but is this
the right fix? Especially since it didn't happen with gcc 14.x, it
does seem like a regression, no?

Could you make a bug report to GCC? Note that they want the
preprocessed source code to be able to easily reproduce.

Thanks a lot!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2026-08-16 15:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-11 11:03 [Buildroot] [PATCH 1/1] package/alsa-lib: force -O2 on i386 with gcc >= 15.x Bernd Kuhls
2026-08-16 15:08 ` Thomas Petazzoni via buildroot [this message]

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=aoHSI9MWvRFbPAWO@windsurf \
    --to=buildroot@buildroot.org \
    --cc=bernd@kuhls.net \
    --cc=thomas.petazzoni@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.