From: Gary Thomas <gthomas@cambridge.redhat.com>
To: Jonathan Larmour <jlarmour@redhat.com>
Cc: Nick Garnett <nickg@redhat.com>,
ecos <ecos-discuss@sourceware.cygnus.com>,
Rafael RodrÃÂguez Velilla <rrv@tid.es>
Subject: Re: [ECOS] HAL_SavedRegisters (ecos 1_3_1)
Date: Thu, 31 May 2001 08:58:00 -0000 [thread overview]
Message-ID: <XFMail.20010531095806.gthomas@cambridge.redhat.com> (raw)
In-Reply-To: <3B166695.984C3F99@redhat.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 852 bytes --]
On 31-May-2001 Jonathan Larmour wrote:
> Rafael RodrÃguez Velilla wrote:
>>
>> I can't find any place where the member msr of the struct
>> HAL_SavedRegisters is used (I have reviewed only the ARM
>> implementation). I think that this member should be omitted from the
>> struct.
>
>From what I can see you are right (although Gary should probably confirm).
> The only thing is that if we remove it now, it may cause incompatibilities
> between a GDB stub in ROM and applications, if built from different
> sources, since ARMREG_SIZE in vectors.S will have changed.
I'm pretty sure that I defined that register _just in case_ it was important.
It might still be with some future version of the ARM chip.
I'd rather not remove it, both to retain pure compatability and for stability
reasons. I also don't see much benefit from saving 4 bytes.
next prev parent reply other threads:[~2001-05-31 8:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-30 10:36 Rafael RodrÃguez Velilla
2001-05-30 12:13 ` [ECOS] " Fabrice Gautier
2001-05-31 0:17 ` Rafael RodrÃguez Velilla
2001-05-31 8:43 ` [ECOS] " Jonathan Larmour
2001-05-31 8:51 ` Nick Garnett
2001-05-31 8:58 ` Gary Thomas [this message]
2001-06-01 8:11 ` 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=XFMail.20010531095806.gthomas@cambridge.redhat.com \
--to=gthomas@cambridge.redhat.com \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=jlarmour@redhat.com \
--cc=nickg@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).