From: Rafael RodrÃÂguez Velilla <rrv@tid.es>
To: ecos <ecos-discuss@sourceware.cygnus.com>
Subject: Re: [ECOS] HAL_SavedRegisters (ecos 1_3_1)
Date: Fri, 01 Jun 2001 08:11:00 -0000 [thread overview]
Message-ID: <3B17AAC2.D5FFCA54@tid.es> (raw)
In-Reply-To: <XFMail.20010531095806.gthomas@cambridge.redhat.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1132 bytes --]
Gary Thomas wrote:
> 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.
What about using a cdl option to let the user decide if he wants that kind of
backward compatibility?
--
Rafael RodrÃguez Velilla rrv@tid.es
Telefónica I+D http://www.tid.es
Telf: +34 - 91 337 4270
prev parent reply other threads:[~2001-06-01 8:11 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
2001-06-01 8:11 ` Rafael RodrÃguez Velilla [this message]
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=3B17AAC2.D5FFCA54@tid.es \
--to=rrv@tid.es \
--cc=ecos-discuss@sourceware.cygnus.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).