public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Deepesh Varatharajan <deepesh.varatharajan@windriver.com>
To: openembedded-core@lists.openembedded.org
Cc: Sundeep.Kokkonda@windriver.com
Subject: Re: [PATCH] conf/bitbake.conf: Remove debug flags for native and nativesdk builds
Date: Thu, 23 Oct 2025 17:23:29 +0530	[thread overview]
Message-ID: <df752f42-1849-4913-ac24-ed5b3b63164e@windriver.com> (raw)
In-Reply-To: <20251023113444.882980-1-Deepesh.Varatharajan@windriver.com>

Hi All,

Testing results :

qemux86-64

time taken for bitbake clang & bitbake gcc for debug builds

with (-g -Og)                        with(-O2)            Diff
  real    46m43.329s             real    41m28.778s             -5m 14.551s
  user    0m22.136s              user    0m22.134s -0.002s
  sys     0m3.048s                  sys     0m3.020s  -0.028s

tmp Dir
size 86 GB                            size 38 GB           -48 GB


qemuarm64

time taken for bitbake clang & bitbake gcc  for debug builds

  with (-g -Og)                       with(-O2)          Diff
  real    48m26.788s            real    41m46.814s            -6m 39.974s
  user    0m30.930s             user    0m21.854s  -9.076s
  sys     0m4.068s                 sys     0m3.085s -0.983s

tmp Dir
size 92 GB                            size 41 GB        -51 GB

Regards,
Deepesh

On 23-10-2025 17:04, Deepesh.Varatharajan@windriver.com wrote:
> From: Deepesh Varatharajan <Deepesh.Varatharajan@windriver.com>
>
> The native and nativesdk builds were previously using the '-Og -g' flags
> during debug builds. This resulted in increased disk usage and few linker
> memory issues due to the large debug information generated.
>
> Since native and nativesdk components do not require debug symbols,
> update the build flags to use '-O2' instead of '-Og -g' for these builds.
> This reduces build size and avoids memory-related issues during linking.
>
> Signed-off-by: Deepesh Varatharajan <Deepesh.Varatharajan@windriver.com>
> ---
>   meta/conf/bitbake.conf | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
> index 5406e542db..d8f9f6c312 100644
> --- a/meta/conf/bitbake.conf
> +++ b/meta/conf/bitbake.conf
> @@ -663,7 +663,7 @@ DEBUG_OPTIMIZATION = "-Og ${DEBUG_LEVELFLAG}"
>   SELECTED_OPTIMIZATION = "${@d.getVar(oe.utils.vartrue('DEBUG_BUILD', 'DEBUG_OPTIMIZATION', 'FULL_OPTIMIZATION', d))}"
>   SELECTED_OPTIMIZATION[vardeps] += "FULL_OPTIMIZATION DEBUG_OPTIMIZATION DEBUG_BUILD"
>   # compiler flags for native/nativesdk
> -BUILD_OPTIMIZATION = "${@oe.utils.vartrue('DEBUG_BUILD', '-Og -g', '-O2', d)}"
> +BUILD_OPTIMIZATION = '-O2'
>   BUILD_OPTIMIZATION[vardeps] += "DEBUG_BUILD"
>   
>   ##################################################################

  reply	other threads:[~2025-10-23 11:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-23 11:34 [PATCH] conf/bitbake.conf: Remove debug flags for native and nativesdk builds Deepesh.Varatharajan
2025-10-23 11:53 ` Deepesh Varatharajan [this message]
2025-10-23 12:00 ` [OE-core] " Peter Kjellerstedt
2025-10-23 12:41   ` Alexander Kanavin

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=df752f42-1849-4913-ac24-ed5b3b63164e@windriver.com \
    --to=deepesh.varatharajan@windriver.com \
    --cc=Sundeep.Kokkonda@windriver.com \
    --cc=openembedded-core@lists.openembedded.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