public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Lewin A.R.W. Edwards" <larwe@larwe.com>
To: Jonathan Larmour <jlarmour@redhat.com>,
	Robert Ritchey <RRRitchey@ACM.Org>,
	ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Size?
Date: Thu, 01 Mar 2001 13:22:00 -0000	[thread overview]
Message-ID: <4.3.2.7.2.20010301161636.00bb2280@mail.larwe.com> (raw)
In-Reply-To: <3A9EB681.F42BDE02@redhat.com>

>And also the architecture - ARM vs. Thumb is a factor of two difference in
>code size straight off. BTW I doubt it is easy to guess RAM memory usage

This reminds - Jonathan, you posted me some instructions on building the 
gcc libs with thumb interwork support, so I could get my app built in 
-mthumb mode and eCos built in non-thumb mode. Those instructions did in 
fact work for me (Linux).

Now, if only it was possible to get thumb tools working in Windows... or 
the current CVS sources to configure in Windows... grrr, mumble, mumble, 
mumble, I'm stuck with 1.3.1 and no networking again, mumble, grumble.

=== Lewin A.R.W. Edwards (Embedded Engineer)
Work: http://www.digi-frame.com/
Personal: http://www.zws.com/ and http://www.larwe.com/

"Und setzet ihr nicht das Leben ein,
Nie wird euch das Leben gewonnen sein."

  reply	other threads:[~2001-03-01 13:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-01 12:35 Robert Ritchey
2001-03-01 12:50 ` Jonathan Larmour
2001-03-01 12:52   ` Jonathan Larmour
2001-03-01 13:22     ` Lewin A.R.W. Edwards [this message]
2001-03-01 13:29       ` Jonathan Larmour
2001-03-01 14:25         ` Lewin A.R.W. Edwards
2001-03-01 15:36   ` Robert Ritchey
2001-03-01 15:41     ` Jonathan Larmour
2001-03-01 19:51       ` Robert Ritchey
2001-03-01 14:48 Rosimildo daSilva
2001-03-01 15:02 ` Lewin A.R.W. Edwards
2001-03-01 15:15 ` Jonathan Larmour
2001-03-01 15:44   ` Lewin A.R.W. Edwards
2001-03-01 18:27 Rosimildo daSilva

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=4.3.2.7.2.20010301161636.00bb2280@mail.larwe.com \
    --to=larwe@larwe.com \
    --cc=RRRitchey@ACM.Org \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=jlarmour@redhat.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).