From: Andre McCurdy <armccurdy@yahoo.co.uk>
To: law@cygnus.com
Cc: gcc@gcc.gnu.org
Subject: Re: MIPS16 -mentry pseudo instruction definitions
Date: Thu, 09 Sep 1999 07:06:00 -0000 [thread overview]
Message-ID: <19990909140529.8571.rocketmail@web601.yahoomail.com> (raw)
--- Jeffrey A Law <law@cygnus.com> wrote:
>
> In message
>
< 19990908183055.2659.rocketmail@web601.yahoomail.com >you
> write:
> > Does anyone have a description of exactly what
> the
> > 'entry' and 'exit' pseudo instructions
> (generated with
> > the -mips16 -mentry options for MIPS targets)
> require
> > of a trap exception handler in order for them to
> be
> > used ?
> >
> > Is there are formal definition somewhere
> describing
> > what they do ?
> I would check the mips16 ISA.
>
> jeff
>
Do you have a URL for such a document ?
Actually, although I haven't seen an official mip16
ISA spec, I thought the entry/exit pseudo instructions
were a Cygnus and/or gcc addition rather than being
part of the spec ??
Andre
--
____________________________________________________________
Do You Yahoo!?
Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk
or your free @yahoo.ie address at http://mail.yahoo.ie
WARNING: multiple messages have this Message-ID
From: Andre McCurdy <armccurdy@yahoo.co.uk>
To: law@cygnus.com
Cc: gcc@gcc.gnu.org
Subject: Re: MIPS16 -mentry pseudo instruction definitions
Date: Thu, 30 Sep 1999 18:02:00 -0000 [thread overview]
Message-ID: <19990909140529.8571.rocketmail@web601.yahoomail.com> (raw)
Message-ID: <19990930180200.czXJ9pU8gcEOcRjv5vzv8ImiEtPyuVLzhjqGjT9UGgo@z> (raw)
--- Jeffrey A Law <law@cygnus.com> wrote:
>
> In message
>
< 19990908183055.2659.rocketmail@web601.yahoomail.com >you
> write:
> > Does anyone have a description of exactly what
> the
> > 'entry' and 'exit' pseudo instructions
> (generated with
> > the -mips16 -mentry options for MIPS targets)
> require
> > of a trap exception handler in order for them to
> be
> > used ?
> >
> > Is there are formal definition somewhere
> describing
> > what they do ?
> I would check the mips16 ISA.
>
> jeff
>
Do you have a URL for such a document ?
Actually, although I haven't seen an official mip16
ISA spec, I thought the entry/exit pseudo instructions
were a Cygnus and/or gcc addition rather than being
part of the spec ??
Andre
--
____________________________________________________________
Do You Yahoo!?
Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk
or your free @yahoo.ie address at http://mail.yahoo.ie
next reply other threads:[~1999-09-09 7:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-09 7:06 Andre McCurdy [this message]
1999-09-09 14:42 ` Richard Henderson
1999-09-30 18:02 ` Richard Henderson
1999-09-30 18:02 ` Andre McCurdy
-- strict thread matches above, loose matches on Subject: below --
1999-09-14 7:07 Andre McCurdy
1999-09-30 18:02 ` Andre McCurdy
1999-09-13 5:53 Andre McCurdy
1999-09-13 8:52 ` Rask Ingemann Lambertsen
1999-09-30 18:02 ` Rask Ingemann Lambertsen
1999-09-13 12:32 ` Jim Wilson
1999-09-30 18:02 ` Jim Wilson
1999-09-30 18:02 ` Andre McCurdy
1999-09-10 8:21 Andre McCurdy
1999-09-10 11:57 ` Jim Wilson
1999-09-30 18:02 ` Jim Wilson
1999-09-30 18:02 ` Andre McCurdy
1999-09-08 11:33 Andre McCurdy
1999-09-08 14:05 ` Jeffrey A Law
1999-09-30 18:02 ` Jeffrey A Law
1999-09-30 18:02 ` Andre McCurdy
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=19990909140529.8571.rocketmail@web601.yahoomail.com \
--to=armccurdy@yahoo.co.uk \
--cc=gcc@gcc.gnu.org \
--cc=law@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).