From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>, Andre McCurdy <armccurdy@gmail.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: gcc-runtime: Remove -mcpu=cortex-a7 when building for -march=armv7ve
Date: Tue, 29 May 2018 21:12:15 +0100 [thread overview]
Message-ID: <1527624735.16911.121.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAMKF1sqSR7chwbVcTVVSqO9Fhg_N=fCqtFK20v=LM1cRe2mO2g@mail.gmail.com>
On Tue, 2018-05-29 at 12:13 -0700, Khem Raj wrote:
> On Tue, May 29, 2018 at 11:41 AM, Andre McCurdy <armccurdy@gmail.com>
> wrote:
> >
> > This change looks wrong (or at least incomplete and lacking a
> > decent
> > explanation):
> why do you think it is wrong ? I would be happy to make the
> explanation more decent
> if you have ideas please share.
>
> >
> >
> > http://git.openembedded.org/openembedded-core/commit/?h=master-ne
> > xt&id=fbec01f01fdad23d95271db063ee0a4d0ab44568
> >
> > It was never posted to the list but seems to have made it as far as
> > master-next.
I don't know where Ross got the patches from but I've taken over and he
told me the patches in mut were ready. I didn't take this one however.
My concern is the use of "remove" which I really prefer not to use in
OE-Core. In core, its a sign that we have the overall structure wrong
as we should never need to do this.
I'd like to understand why gcc-runtime needs this special treatment and
whether there are other arm tunes which have the same issue? Should we
be tweaking the main tune files in some way instead?
Cheers,
Richard
next prev parent reply other threads:[~2018-05-29 20:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-29 18:41 gcc-runtime: Remove -mcpu=cortex-a7 when building for -march=armv7ve Andre McCurdy
2018-05-29 19:13 ` Khem Raj
2018-05-29 20:12 ` Richard Purdie [this message]
2018-05-30 1:58 ` Khem Raj
2018-05-29 20:34 ` Andre McCurdy
2018-05-30 2:06 ` 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=1527624735.16911.121.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=armccurdy@gmail.com \
--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