From: Martin Jansa <martin.jansa@gmail.com>
To: Andre McCurdy <armccurdy@gmail.com>
Cc: Yocto Project <yocto@yoctoproject.org>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
openembedded-devel <Openembedded-devel@lists.openembedded.org>
Subject: Re: [RFT] GCC 8.1
Date: Fri, 11 May 2018 01:32:33 +0200 [thread overview]
Message-ID: <20180510233233.GF1954@jama> (raw)
In-Reply-To: <CAJ86T=UfXtgtaWQyJbrhW40MJFW9YAArB3CshMxy5e5f9Cg_=Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1448 bytes --]
On Thu, May 10, 2018 at 04:11:00PM -0700, Andre McCurdy wrote:
> On Thu, May 10, 2018 at 3:50 PM, Martin Jansa <martin.jansa@gmail.com> wrote:
> > On Thu, May 10, 2018 at 03:40:53PM -0700, Andre McCurdy wrote:
> >> On Thu, May 10, 2018 at 3:38 PM, Martin Jansa <martin.jansa@gmail.com> wrote:
> >> > see
> >> > http://lists.openembedded.org/pipermail/openembedded-core/2018-May/150654.html
> >>
> >> Removing -fno-omit-frame-pointer isn't the same as adding
> >> -fomit-frame-pointer. Frame pointers may get enabled depending on the
> >> optimisation level etc (ie not only by -fno-omit-frame-pointer).
> >
> > Should I send v2 adding -fomit-frame-pointer instead of removing
> > -fno-omit-frame-pointer?
> >
> > The v1 fixes the issue for me with default config + DEBUG_BUILD.
>
> The v1 patch isn't wrong, it's just incomplete (the problem could come
> back if someone changes optimisation level or switches gcc to clang,
> etc).
>
> My choice would be a v2 patch which adds -fomit-frame-pointer to
> CFLAGS unconditionally for all ARM builds when Thumb is enabled. That
> should fix the problem for all optimisation levels etc and avoids
> building the main strace binary differently depending on whether or
> not ptest is enabled.
Only for thumb? makes me a bit sad that thumb override was dropped by
you in
351443d71eb246a946b41f12b54d57b36fe1574e
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]
next prev parent reply other threads:[~2018-05-10 23:32 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-05 0:26 [RFT] GCC 8.1 Khem Raj
2018-05-09 9:38 ` Martin Jansa
2018-05-10 12:20 ` [PATCH] busybox: Enable FEATURE_MOUNT_NFS and use libtirpc Martin Jansa
2018-05-10 13:01 ` Burton, Ross
2018-05-10 18:21 ` Khem Raj
2018-05-10 18:24 ` Khem Raj
2018-05-10 19:16 ` Martin Jansa
2018-05-10 19:26 ` Khem Raj
2018-05-30 17:39 ` Andre McCurdy
2018-06-10 11:05 ` Martin Jansa
2018-05-10 18:50 ` [RFT] GCC 8.1 Khem Raj
2018-05-10 19:11 ` Martin Jansa
2018-05-10 19:27 ` Andre McCurdy
2018-05-10 21:43 ` Martin Jansa
2018-05-10 22:07 ` Martin Jansa
2018-05-10 22:35 ` Khem Raj
2018-05-10 22:38 ` Andre McCurdy
2018-05-10 22:38 ` Martin Jansa
2018-05-10 22:40 ` Andre McCurdy
2018-05-10 22:50 ` Martin Jansa
2018-05-10 23:11 ` Andre McCurdy
2018-05-10 23:32 ` Martin Jansa [this message]
2018-05-10 23:41 ` Andre McCurdy
2018-05-11 0:55 ` Khem Raj
2018-05-11 1:00 ` Andre McCurdy
2018-05-11 1:06 ` Khem Raj
2018-05-11 1:11 ` Andre McCurdy
2018-05-11 1:16 ` Khem Raj
2018-05-11 1:21 ` Andre McCurdy
2018-05-17 10:46 ` Martin Jansa
2018-05-18 5:54 ` Khem Raj
2018-05-24 15:08 ` Martin Jansa
2018-05-10 14:34 ` Dan McGregor
2018-05-10 18:53 ` Khem Raj
2018-05-14 16:33 ` Dan McGregor
2018-05-14 17:09 ` Martin Jansa
[not found] ` <CAGAf8LxceSXvK-pgfWYDvYLmcvMMK0D5q==PKG9jeRWs6YEbGA@mail.gmail.com>
2018-05-10 19:21 ` [yocto] " Khem Raj
2018-05-11 22:05 ` Burton, Ross
2018-05-12 6:10 ` Khem Raj
2018-05-13 23:35 ` Khem Raj
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=20180510233233.GF1954@jama \
--to=martin.jansa@gmail.com \
--cc=Openembedded-devel@lists.openembedded.org \
--cc=armccurdy@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=yocto@yoctoproject.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