public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <hongxu.jia@eng.windriver.com>,
	<openembedded-core@lists.openembedded.org>
Cc: <randy.macleod@windriver.com>, <peter.kjellerstedt@axis.com>
Subject: Re: [OE-core] [PATCH 4/8] debug_build.inc: collect debug build tuning configuration
Date: Wed, 17 Sep 2025 13:24:42 +0200	[thread overview]
Message-ID: <DCV1DEVKB7V0.2YZ96FPV5N3X6@bootlin.com> (raw)
In-Reply-To: <20250916040927.103722-4-hongxu.jia@windriver.com>

On Tue Sep 16, 2025 at 6:09 AM CEST, hongxu via lists.openembedded.org wrote:
> The modern compilers and code seem to require extra steps to avoid DEBUG errors,
> Move debug tuning configuration from recipes to an include file to address these
> errors.
>
> Introduce separate variables to avoid the :remove operations, such DEBUG_OPTLEVEL,
> BUILD_OPTLEVEL and OECMAKE_WEBKIT_NO_INLINE_HINTS
>
> Suggested-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
> Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
> ---

Just a note about this patches: I had perf reproducibility issues [1][2]
after taking this series and I believe this is linked with this patch. I
suspect this is not directly related with it, but more with the issue we
have had with perf reproducibility last week.

So I dropped this patch for now, but I will take it a bit later this
week and try to go further. I still wanted to provide some feedback
here. Also, if anyone believes this issue IS related with this series,
please share your thoughts.

[1] https://autobuilder.yoctoproject.org/valkyrie/#/builders/37/builds/2505
[2] http://valkyrie.yocto.io/pub/repro-fail/oe-reproducible-20250916-0ss72vce/

Thanks,
Mathieu

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



  reply	other threads:[~2025-09-17 11:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-16  4:09 [PATCH 1/8] yocto-space-optimize.inc: move space optimize from recipe webkitgtk Hongxu Jia
2025-09-16  4:09 ` [PATCH v3 2/8] distro/include: Add debug_build.inc when DEBUG_BUILD is enabled Hongxu Jia
2025-09-29 18:48   ` [OE-core] " Khem Raj
2025-09-29 22:52     ` Peter Kjellerstedt
2025-10-10  7:37       ` Hongxu Jia
2025-09-16  4:09 ` [PATCH 3/8] harfbuzz: set FULL_OPTLEVEL for FULL_OPTIMIZATION Hongxu Jia
2025-09-16  4:09 ` [PATCH 4/8] debug_build.inc: collect debug build tuning configuration Hongxu Jia
2025-09-17 11:24   ` Mathieu Dubois-Briand [this message]
2025-09-17 12:15     ` hongxu
2025-09-19  3:08     ` [OE-core] " Hongxu Jia
     [not found]     ` <1866903FE1AA84E8.22280@lists.openembedded.org>
2025-09-19  8:34       ` Hongxu Jia
2025-09-21  6:30     ` Mathieu Dubois-Briand
2025-09-16  4:09 ` [PATCH v3 5/8] debug_build.inc: allow other layers to add their own debug build configurations Hongxu Jia
2025-09-16  4:09 ` [PATCH 6/8] debug_build.inc: override INHIBIT_SYSROOT_STRIP for cross and native Hongxu Jia
2025-09-16  4:09 ` [PATCH 7/8] debug_build.inc: override MESON_BUILDTYPE for meson.bbclass Hongxu Jia
2025-09-16  4:09 ` [PATCH v3 8/8] debug_build.inc: override BUILD_MODE and BUILD_DIR for cargo.bbclass Hongxu Jia

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=DCV1DEVKB7V0.2YZ96FPV5N3X6@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=hongxu.jia@eng.windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=peter.kjellerstedt@axis.com \
    --cc=randy.macleod@windriver.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