public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Ilija Kocho [Илија Кочо]" <ilijak@siva.com.mk>
To: Stanislav Meduna <stano@meduna.org>,
	"ecos-discuss@sourceware.org" <ecos-discuss@sourceware.org>
Subject: Re: [ECOS] eCos and Keil
Date: Mon, 30 May 2016 10:05:00 -0000	[thread overview]
Message-ID: <574C1063.3080002@siva.com.mk> (raw)
In-Reply-To: <56B22002.7010503@meduna.org>

Hi Stano,

I am playing with GCC 6.1 and it gives 20% beetter Coremark than GCC 4.9.

I would like to submit GCC 6.1 as a replacement for GCC 4.6 but there's
one important issue with GCC 5.0 and newer. Namely, they have adopted
GCC 11 as standard mode rather than 89. which mainly affects inlining.
For the time being I have solved this problem by enforcing 89 mode on
GCC, but I am in a dilemma whether to:

   1. Enforce mode 89 (as I do now)
   2. Make eCos to work in C11 mode. In this case I will need some help.

Regards

Ilija





On 03.02.2016 16:42, Stanislav Meduna wrote:
> Hi,
>
> did anybody try to tweak the eCos to allow building with Keil
> MDK-ARM?
>
> The thing is Keil produces _much_ smaller (a saving of 1/3
> is often doable) and faster code. For embedded systems
> this matters a lot.
>
> I understand that this is not trivial, as some of the code
> is dependent on gcc-specific features and the build system
> is tailored to the GNU tools.
>
> Thanks


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

      reply	other threads:[~2016-05-30 10:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-03 15:43 Stanislav Meduna
2016-05-30 10:05 ` Ilija Kocho [Илија Кочо] [this message]

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=574C1063.3080002@siva.com.mk \
    --to=ilijak@siva.com.mk \
    --cc=ecos-discuss@sourceware.org \
    --cc=stano@meduna.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).