From: Adrian Bunk <bunk@stusta.de>
To: Khem Raj <raj.khem@gmail.com>
Cc: Yocto Project <yocto@yoctoproject.org>,
openembedded-architecture
<openembedded-architecture@lists.openembedded.org>,
openembeded-devel <Openembedded-devel@lists.openembedded.org>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [Openembedded-architecture] Dropping armv5 and armv5e tunes in 2.7
Date: Fri, 4 Jan 2019 00:59:15 +0200 [thread overview]
Message-ID: <20190103225915.GB29139@localhost> (raw)
In-Reply-To: <CAMKF1sooPOtN-Y=0_cZ=Qv2viS5mwJAsm+yVsHpOJ5gpN65eZw@mail.gmail.com>
On Thu, Jan 03, 2019 at 02:01:42PM -0800, Khem Raj wrote:
> Hello All
>
> You might have noticed a recent commit in gcc trunk
>
> https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=b232e6b58e3766bc66fe08fdb7bcba1bdadda8a2
>
> Which removed support for deprecated -march=armv5 and armv5e, this
> will be released along with gcc-9 release which is upcoming and we
> might be able to add gcc9 to 2.7 release or 2.8 release for sure.
>
> We still have non-thumb tunes for armv5 and armv4 in our tune pack, I
> would like to propose a patch to remove them.
>...
Note that gcc 9 does *not* remove non-thumb armv4 support.
Non-thumb armv5/armv5e have been removed due to
"have no known implementations".
Non-thumb armv4 support was deprecated in gcc 6 together with armv2/armv3,
but there are still people using recent gcc on StrongARM - which is
non-thumb armv4.
> Thanks
> -Khem
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2019-01-03 22:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 22:01 Dropping armv5 and armv5e tunes in 2.7 Khem Raj
2019-01-03 22:59 ` Adrian Bunk [this message]
2019-01-03 23:21 ` [Openembedded-architecture] " Khem Raj
2019-01-04 12:10 ` Andrea Adami
2019-01-06 3:57 ` Trevor Woerner
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=20190103225915.GB29139@localhost \
--to=bunk@stusta.de \
--cc=Openembedded-devel@lists.openembedded.org \
--cc=openembedded-architecture@lists.openembedded.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--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