From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2019-05-14
Date: Thu, 16 May 2019 11:06:16 +0200 [thread overview]
Message-ID: <20190516110616.329beae6@windsurf> (raw)
In-Reply-To: <20190516115248.GB25918@momiji>
Hello,
+Samuel Martin in the discussion.
On Thu, 16 May 2019 11:52:48 +0300
Adrian Perez de Castro <aperez@igalia.com> wrote:
> > This build has BR2_ENABLE_DEBUG=y, and when BR2_ENABLE_DEBUG=y, the
> > CMake package infrastructure passes -DCMAKE_BUILD_TYPE=Debug. I assume
> > that's under this condition that assertions become enabled.
>
> On a related note: for debug builds done by packagers we usually recommend
> building with ?-DCMAKE_BUILD_TYPE=RelWithDebInfo? because using the ?Debug?
> produces excruciatingly slow WebKit binaries. To give you an idea: loading
> some simple static HTML page over the network can take a couple of minutes.
> Typically full ?Debug? builds are only ever used by WebKit developers.
I know there was so back and forth between Debug and RelWithDebInfo,
see the commit log of commit 104bb29e0490bfb487e2e665448dd3ca07fcc2b5:
commit 104bb29e0490bfb487e2e665448dd3ca07fcc2b5
Author: Samuel Martin <s.martin49@gmail.com>
Date: Sun Oct 16 13:12:37 2016 +0200
Revert "package/cmake: with BR2_ENABLE_DEBUG use RelWithDebInfo"
This reverts commit 4b0120183404913f7f7788ef4f0f6b51498ef363.
Before reverting this patch, CMake packages are built with the following
options:
* if BR2_ENABLE_DEBUG is set:
The CMake build type is set to RelWithDebInfo, which means:
- Optimization level is forced to: -O2;
- no log nor assert due to -DNDEBUG;
- BR2_DEBUG_{1..3} effect is unchanged;
* otherwise:
The CMake build type is set to Release, which means:
- Optimization level is forced to: -O3;
- no log nor assert due to -DNDEBUG (as expected).
In any case, the optimization WRT the binary size is always ignored
and forced.
Reverting to the previous situation, so Buildroot now chooses between
the 'Debug' and 'Release' config types, which are semantically closer
to what Buildroot does everywhere else:
* if BR2_ENABLE_DEBUG is set:
The CMake build type is set to Debug, which means:
- only -g option is passed by CMake;
- optimization is not forced, nor debug level, so they are kept
as-is;
* otherwise:
The CMake build type is set to Release, so no change in this case:
- Optimization level is forced to: -O3;
- no log nor assert due to -DNDEBUG (as expected);
- size optimization is ignored.
Follow-up patches will fix the CMake flag variables that are appended by
CMake.
Cc: Charles Hardin <ckhardin@exablox.com>
Cc: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Cc: Maxime Hadjinlian <maxime.hadjinlian@gmail.com>
Signed-off-by: Samuel Martin <s.martin49@gmail.com>
Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
So apparently, the issue with RelWithDebInfo is that it forces the
optimization level.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-05-16 9:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-15 6:00 [Buildroot] [autobuild.buildroot.net] Build results for 2019-05-14 Thomas Petazzoni
2019-05-15 19:17 ` Adrian Perez de Castro
2019-05-16 6:33 ` Thomas Petazzoni
2019-05-16 8:52 ` Adrian Perez de Castro
2019-05-16 9:06 ` Thomas Petazzoni [this message]
2019-05-26 11:35 ` Arnout Vandecappelle
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=20190516110616.329beae6@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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