From: "Mikko Rapeli" <mikko.rapeli@bmw.de>
To: <raj.khem@gmail.com>
Cc: <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 2/2] lz4: use CFLAGS from bitbake
Date: Fri, 23 Apr 2021 05:49:07 +0000 [thread overview]
Message-ID: <YIJf0rTBgrKAtI3B@korppu> (raw)
In-Reply-To: <CAMKF1sq8YwMNdL7f-COjZLDxzNL=8CPrZmX-1WwDqYZc=aASOQ@mail.gmail.com>
On Thu, Apr 22, 2021 at 08:05:20AM -0700, Khem Raj wrote:
> On Thu, Apr 22, 2021 at 7:42 AM Mikko Rapeli <mikko.rapeli@bmw.de> wrote:
>
> > Currently lz4 uses it's own defaults which include O3 optimization.
> > Switch from O3 to bitbake default O2 reduces binary package size
> > from 467056 to 331888 bytes. Enables also building with Os if needed.
>
>
> These could impact runtime performance have you
> Checked what the rough impact is ?
Nope, have not checked this. I've build my targets with this patch
and have not noticed any major performance regression. If there is
a performance problem, then I'd rather see O3 explicitly set in the recipe,
for example for native target.
> Secondly we will be using non default set which could result in errors less
> seen by others over time I have realized it’s also good to open a dialog
> upstream and get the reasoning behind not letting distro defaults apply
> some packages do have valid reasons
I've seen bugs with O3 optimziation level too on some target archs.
I would not enable that by default. But I do understand your concern.
In similar ways, I was checking ffmpeg, attr, acl etc which were defaulting
to O3 in older versions but with new poky master versions now behave well
and use bitbake default O2. I guess there too no major performance regressions
have been detected.
Cheers,
-Mikko
next prev parent reply other threads:[~2021-04-23 5:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 14:41 [PATCH 2/2] lz4: use CFLAGS from bitbake Mikko Rapeli
2021-04-22 15:05 ` [OE-core] " Khem Raj
2021-04-23 5:49 ` Mikko Rapeli [this message]
2021-04-23 6:00 ` Khem Raj
2021-04-23 7:22 ` Mikko Rapeli
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=YIJf0rTBgrKAtI3B@korppu \
--to=mikko.rapeli@bmw.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.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