public inbox for
 help / color / mirror / Atom feed
From: Ken <>
Subject: Re: gcc for embedded: Worth it?
Date: Mon, 29 Jun 1998 21:31:00 -0000	[thread overview]
Message-ID: <> (raw)

Martin Boyer wrote:
> "Martin Weiss" <> writes:
> > Who has ever tried to compile a crosscompiler under linux to run
> > under win32 and to target 68k? Experiences with c++ for embedded?
> I didn't have time to built the crosscompiler myself, so I had my
> company purchase GNUPro, from Cygnus Solutions.  This is for an Intel
> i960 target on a Windows NT 4.0 host.
> After a few weeks of early problems, caused mainly by problems with
> segmentation faults from an older version of cygwin32, I can say this
> was a very good decision.  The folks at Cygnus are very competent and
> diligent.  The tools are good and easy to use (I'm a Unix old-timer).
> As for C++ for embedded, we had a protocol library that was using
> templates and the Standard Template Library.  That never worked, most
> probably due to problems with constructors or structure
> initialization.  I can't blame anyone; the protocol code was developed
> on Visual C++ 5.0 and used extensions that weren't in the C++ draft
> standard.  To make a long story short, the parts that used templates
> were re-implemented without templates, and that worked.  We have since
> added code which used templates in a limited way, and that worked as
> well.  Go figure.
> Overall, I'd say that GNUPro can generate useful, embeddable, code
> from C++ sources, using inherited classes, constructors, templates (to
> some extent), etc.  I would say that using C++ allowed for a very
> generic protocol library to be created (the same code runs in Visual
> C++ on the control station, and in GNUPro's C++ in the embedded
> system), at the cost of at least double the ROM and RAM requirements
> over a "low-tech" C implementation.  That is a lot when you have 512k
> of each.
> Martin

What accounted for the doubling in size going from C to C++?

[I'm cc'ing this to the new c++-embedded list hosted at Cygnus. Send
subscription requests to .]

mailto:shiva@CompuServe.COM (Death to Spam!)

             reply	other threads:[~1998-06-29 21:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-06-29 21:31 Ken [this message]
     [not found] <6l86kv$>
     [not found] ` <>
     [not found]   ` <>
     [not found]     ` <6mhdu7$fav$>
     [not found]       ` <jEOj1.3654$9Y1.32042@eagle>
     [not found]         ` <3592d3ce.11558168@>
     [not found]           ` <6mvht3$orp$>
     [not found]             ` <x7emwcz757.fsf@carette.Foo.COM>
1998-06-26 21:22               ` Ken

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).