From: Peter Korsgaard <peter@korsgaard.com>
To: Julien Olivain <ju.o@free.fr>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] package/pixman: backport patch to fix inlining issue
Date: Wed, 8 Jan 2025 22:37:19 +0100 [thread overview]
Message-ID: <250c0879-722b-4739-bca9-a5f4c7d6ec0e@korsgaard.com> (raw)
In-Reply-To: <211624fb7afbbb83eb709499c2f37802@free.fr>
On 1/3/25 22:43, Julien Olivain wrote:
> On 03/01/2025 21:17, Thomas Petazzoni wrote:
>> pixman fails to build with -Og or -O3 due to forced inlining
>> statements:
>>
>> pixman-combine-float.c:370:5: error: inlining failed in call to
>> 'always_inline' 'combine_soft_light_c': function not considered for
>> inlining
>>
>> The first occurence in the autobuilders is on May 12, 2024, but the
>> problem already existed before as we haven't updated pixman in a long
>> time. Therefore, the issue started occurring because we started
>> testing more random configurations.
>>
>> Fixes:
>>
>> https://autobuild.buildroot.org/
>> results/2f3df7961b3181d9eef79893439ae7ebbe4415ad/
>>
>> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Committed to 2024.02.x and 2024.11.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2025-01-08 21:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-03 20:17 [Buildroot] [PATCH 1/2] package/pixman: backport patch to fix inlining issue Thomas Petazzoni
2025-01-03 20:17 ` [Buildroot] [PATCH 2/2] package/pixman: bump to version 0.44.2 Thomas Petazzoni via buildroot
2025-01-03 21:43 ` [Buildroot] [PATCH 1/2] package/pixman: backport patch to fix inlining issue Julien Olivain
2025-01-08 21:37 ` Peter Korsgaard [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=250c0879-722b-4739-bca9-a5f4c7d6ec0e@korsgaard.com \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=ju.o@free.fr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).