From: Frank Pagliughi <fpagliughi@mindspring.com>
To: Ilija Kocho <ilijak@siva.com.mk>
Cc: eCos developers <ecos-devel@ecos.sourceware.org>
Subject: Re: Gnutools: consideration for upgrade to GCC 4.6
Date: Fri, 13 Jan 2012 19:09:00 -0000 [thread overview]
Message-ID: <4F108164.8010500@mindspring.com> (raw)
In-Reply-To: <4F106345.4080902@siva.com.mk>
On 01/13/2012 12:00 PM, Ilija Kocho wrote:
> Hi colleagues
>
> Our GCC 4.3.2 is ageing and perhaps we should consider an upgrade.
> My motive is it's lacking of support for Cortex-M4 SIMD (aka DSP) and
> FPU instructions, but I think that other architectures shall gain from
> newer compiler too. I have made some signal processing tests with GCC
> 4.6.2 against current eCos compiler and they show performance gain
> even with Cortex-M3 setting, though moderate. Performance is
> considerable when Cortex-M4 setting is selected and is tremendous, as
> expected, when SIMD are used. Recently introduced Cortex-M products
> with FPU (Kinetis K70, K61, STM32F4) will further emphasise the benefit.
>
> Another reason, maybe not so important, is that GCC 4.3 is not
> officially supported any more.
>
> Regarding this, I state my wish that we move to the latest stable GCC
> release, that is at present rel. 4.6.2, accompanied with respective
> binutils. I have tested binutils 2.21 but in meantime 2.22 has been
> released. Of course, the list wouldn't be complete without the latest
> GDB.
>
> Looking forward for your comments.
> Ilija
>
I'm all for it. I've been using 4.6.2 for the last few months for ARM
(EABI, of course) and i386. The 4.3 compilers wouldn't compile some of
the libraries that I use and I didn't want to back port them to an old
compiler. I used binutils 2.21.1.
So far I've been very happy, but I was mostly concerned with language
features. The additional Cortex support sells it, though. I'm just
starting to start shopping around for a Cortex-M3 for my next project.
Frank
next prev parent reply other threads:[~2012-01-13 19:09 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-13 17:01 Ilija Kocho
2012-01-13 18:54 ` Bernard Fouché
2012-01-13 19:39 ` Ilija Kocho
2012-01-13 19:09 ` Frank Pagliughi [this message]
2012-01-13 19:45 ` Ilija Kocho
2012-01-14 10:22 ` John Dallaway
2012-01-14 16:02 ` Sergei Gavrikov
2012-01-15 17:36 ` Grant Edwards
2012-01-15 18:42 ` Sergei Gavrikov
2012-01-15 21:39 ` Stanislav Meduna
2012-01-23 1:01 ` Jonathan Larmour
2012-01-15 22:21 ` Ilija Kocho
2012-01-15 22:21 ` Ilija Kocho
2012-01-23 1:07 ` Jonathan Larmour
2012-01-16 15:20 ` Grant Edwards
2012-01-16 20:43 ` Sergei Gavrikov
2012-01-16 21:11 ` Sergei Gavrikov
2012-01-17 9:58 ` Bernard Fouché
2012-01-17 10:38 ` Paul Beskeen
2012-01-17 12:28 ` Sergei Gavrikov
2012-01-23 0:59 ` Jonathan Larmour
2012-01-14 16:25 ` Ilija Kocho
2012-01-23 1:13 ` Jonathan Larmour
2012-01-23 18:40 ` Ilija Kocho
2012-01-23 19:29 ` Jonathan Larmour
2012-01-25 12:30 ` Alex Schuilenburg
2012-01-25 20:59 ` Ilija Kocho
2012-01-26 13:36 ` Alex Schuilenburg
2012-01-26 20:18 ` Ilija Kocho
2012-02-13 22:02 ` eCos GNU tools 4.6.2-20120125 ready for testing [Was Re: Gnutools: consideration for upgrade to GCC 4.6] Ilija Kocho
2012-02-20 16:00 ` Alex Schuilenburg
2012-02-20 20:45 ` Ilija Kocho
2012-03-02 16:36 ` Alex Schuilenburg
2012-03-03 13:32 ` Ilija Kocho
2012-03-04 0:10 ` Alex Schuilenburg
2012-03-04 17:49 ` Sergei Gavrikov
2012-03-04 23:08 ` Alex Schuilenburg
2012-03-04 19:37 ` eCos GNU tools 4.6.2-20120125 ready for testing John Dallaway
2012-03-04 23:47 ` Alex Schuilenburg
2012-03-05 8:00 ` Sergei Gavrikov
2012-03-07 13:51 ` Sergei Gavrikov
2012-03-07 11:58 ` Alex Schuilenburg
2012-03-07 13:01 ` Ilija Kocho
2012-03-07 13:39 ` Sergei Gavrikov
2012-03-07 13:13 ` John Dallaway
2012-03-12 16:43 ` Alex Schuilenburg
2012-03-16 15:05 ` Alex Schuilenburg
2012-03-08 17:28 ` Alex Schuilenburg
2012-03-09 9:39 ` Ilija Kocho
2012-03-09 17:15 ` Alex Schuilenburg
2012-03-10 17:16 ` John Dallaway
2012-03-12 16:12 ` Alex Schuilenburg
2012-03-13 13:31 ` Alex Schuilenburg
2012-03-13 14:16 ` Ilija Kocho
2012-03-13 17:47 ` Sergei Gavrikov
2012-03-15 8:50 ` John Dallaway
2012-03-17 14:50 ` Sergei Gavrikov
2012-03-17 20:58 ` John Dallaway
2012-03-17 16:44 ` Stanislav Meduna
2012-03-18 19:10 ` eCos GNU tools 4.6.3-20120315 [Was Re: eCos GNU tools 4.6.2-20120125 ready for testing] Ilija Kocho
2012-04-04 12:57 ` Lambrecht Jürgen
2012-04-04 13:18 ` Ilija Kocho
2012-05-31 8:42 ` eCos GNU tools 4.6.3-20120315 and link time optimization Bernard Fouché
2012-03-05 8:30 ` eCos GNU tools 4.6.2-20120125 ready for testing Tomas Frydrych
2012-03-05 8:56 ` Tomas Frydrych
2012-03-05 9:50 ` John Dallaway
2012-03-05 9:55 ` Anders Montonen
2012-03-05 14:20 ` John Dallaway
2012-03-05 10:16 ` Ilija Kocho
2012-03-05 12:56 ` Tomas Frydrych
2012-03-03 12:58 ` eCos GNU tools 4.6.2-20120125 ready for testing [Was Re: Gnutools: consideration for upgrade to GCC 4.6] Sergei Gavrikov
2012-01-17 9:37 ` Gnutools: consideration for upgrade to GCC 4.6 Tomas Frydrych
2012-01-17 16:10 ` Stanislav Meduna
2012-01-17 16:25 ` Tomas Frydrych
2012-01-17 16:45 ` Ilija Kocho
2012-01-20 14:42 ` Frank Pagliughi
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=4F108164.8010500@mindspring.com \
--to=fpagliughi@mindspring.com \
--cc=ecos-devel@ecos.sourceware.org \
--cc=ilijak@siva.com.mk \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).