public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Bart Veer <bartv@redhat.com>
To: rrv@tid.es
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Compiling individual sources
Date: Mon, 10 Sep 2001 08:24:00 -0000	[thread overview]
Message-ID: <200109101524.f8AFOm429420@sheesh.cambridge.redhat.com> (raw)
In-Reply-To: <3B9CC2C9.763E2B26@tid.es>

>>>>> "Rafael" == Rafael =?iso-8859-1?Q?Rodr=EDguez?= Velilla <Rafael> writes:

    Rafael>   I want to compile individual files with -mlong-calls.
    Rafael> Can I use the cdl script to distinguish which files must
    Rafael> be compiled with this switch?

    Rafael>   Maybe, the only way to customice individual files is
    Rafael> using the make command. I'd want to put some of the eCos'
    Rafael> functions in internal memory , but it will have problems
    Rafael> to call the rest of the system if I don't use long-calls.

Some eCos packages will allow you to manipulate the compiler flags on
a per-package basis, but that is as fine-grained as things get right
now. There is no support for manipulating compiler flags on a per-file
basis.

However, I suspect that you will want to use -mlong-calls for all
files, not just for some of them. For example if you want to put a
function like memcpy() into internal memory then either all modules
that invoke memcpy() need to be compiled with -mlong-calls, or
alternatively you need to give the memcpy() function the long-call
attribute in a header file used by all code that calls memcpy(). It is
not enough to compile just memcpy.c with -mlong-calls, that would not
affect any calls to memcpy(). Obviously using -mlong-calls throughout
will involve extra overhead for the system as a whole, which may
outweigh the benefits of having some functions in internal memory.

Bart

  reply	other threads:[~2001-09-10  8:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-10  7:08 Rafael Rodríguez Velilla
2001-09-10  8:24 ` Bart Veer [this message]
2001-09-10  8:43   ` Rafael Rodríguez Velilla
2001-09-10  9:56     ` Bart Veer
2001-09-10 10:23       ` Rafael Rodríguez Velilla

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=200109101524.f8AFOm429420@sheesh.cambridge.redhat.com \
    --to=bartv@redhat.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=rrv@tid.es \
    /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).