public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Alexander Neundorf <neundorf@kde.org>
To: ecos-discuss@ecos.sourceware.org
Cc: Slide <slide.o.mix@gmail.com>
Subject: Re: [ECOS] Non-GCC compiler
Date: Fri, 13 Jul 2007 03:34:00 -0000	[thread overview]
Message-ID: <200707122334.29430.neundorf@kde.org> (raw)
In-Reply-To: <20070712081051.GB15536@lunn.ch>

On Thursday 12 July 2007 04:10, Andrew Lunn wrote:
> On Wed, Jul 11, 2007 at 10:27:08PM -0700, Slide wrote:
> > Has anyone been able to get eCos compiling with a non-GCC based
> > compiler? The processor I would like to port to does not have a GCC
> > toolchain available.
>
> It must be some exotic processor if gcc does not support it.  It will
> be a lot of hard work porting eCos to another tool chain.  Do you have
> the source code to the tool chain you intend to use? You might find it
> useful when you come to work around some of the GCC extensions which
> eCos uses, eg constructor ordering, HAL tables etc.

Some compilers claim to be compatible to gccs extensions, e.g. GreenHills 
(http://www.ghs.com/products/optimizingC++EC++Compilers.html). Which 
toolchain is it ?

Alex

-- 
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:[~2007-07-13  3:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-12  5:27 Slide
2007-07-12  8:10 ` Andrew Lunn
2007-07-13  3:34   ` Alexander Neundorf [this message]
     [not found]     ` <a623f7d10707122136y6e4ae833l4ad2cb99f3dde6b0@mail.gmail.com>
2007-07-13  4:36       ` [ECOS] Fwd: " Slide

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=200707122334.29430.neundorf@kde.org \
    --to=neundorf@kde.org \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=slide.o.mix@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).