public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: James E Wilson <wilson@specifix.com>
To: Torsten Mohr <tmohr@s.netic.de>
Cc: gcc@gcc.gnu.org
Subject: Re: V850 ABI?
Date: Wed, 24 Aug 2005 19:03:00 -0000	[thread overview]
Message-ID: <430CBEA7.1090907@specifix.com> (raw)
In-Reply-To: <200508211312.43162.tmohr@s.netic.de>

Torsten Mohr wrote:
> In that file i've also read about an option "ghs", does
> that one switch to the Greenhills ABI?

In theory, yes.  In practice, I'd be skeptical.  It probably hasn't been
well tested.

> From that file i can't really conclude everything.
> For example i don't know if registers 20 and 21 hold the
> values 255 and 65535 (an optimisation on V850).  The startup
> code in newlib assigns them, but does gcc really rely on that
> and uses that (this question is just an example)?

Try writing a simple example program to check.  Since 20 and 21 are not
fixed registers, my guess would be no.

> Is there a description of the ABI or the ABIs available?

Red Hat probably has a manual.  If you can find a copy of a Red Hat v850
release, there may be a manual inside it that has ABI info.  Otherwise,
probably no.

Gcc normally does not define the ABI.  We just follow ABI standards
produced by others.  You could try checking in NEC publishes an ABI for
the v850.

For some embedded targets, gcc defines the ABI because there isn't an
external one we can follow.  In this case, gcc should document the ABI
that it implements.  This is done for some targets.  If you look, you
can see that some targets have a *ABI* or *abi* file that documents the
gcc abi.  Unfortunately, we don't do this for as many targets as we should.
-- 
Jim Wilson, GNU Tools Support, http://www.specifix.com

      reply	other threads:[~2005-08-24 18:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-21 11:07 Torsten Mohr
2005-08-24 19:03 ` James E Wilson [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=430CBEA7.1090907@specifix.com \
    --to=wilson@specifix.com \
    --cc=gcc@gcc.gnu.org \
    --cc=tmohr@s.netic.de \
    /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).