From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: Re: [9fans] MIPS LSB compiler
Date: Sun, 15 Nov 2009 19:55:36 +0200 [thread overview]
Message-ID: <2b34921287722b84f7f694b134d326e3@proxima.alt.za> (raw)
In-Reply-To: <4AFDB66F.80505@gmx.de>
> correct me if i am wrong. but isn't the usual MIPS calling convention to
> store the return pc in R31?
>
Almost certainly.
> you may just want to look at your compiler output. mips has various
> "branch and link" commands that do a branch and put the returning pc
> into R31, which is the usual calling convention.
As I mentioned, the function isn't even used, so its exact
implementation doesn't matter. What matters is knowing that the
implementation is accurate and my problem is that I don't even know
whether the 64-bit version should be different from the 32-bit
version, I don't understand what differentiates the two alternatives
within the toolchain: how does one choose which version should be
used. Or, if you feel brave, show me what I should submit to Russ for
release. I will happily provide you with a set of patches that works
perfectly happily on my gNewSense, MIPS-64 notebook.
++L
prev parent reply other threads:[~2009-11-15 17:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-13 4:34 lucio
2009-11-13 5:12 ` Roman Shaposhnik
2009-11-13 6:01 ` John Barham
2009-11-13 17:48 ` Tim Newsham
2009-11-13 18:19 ` Iruata Souza
2009-11-13 18:36 ` Tim Newsham
2009-11-15 16:52 ` lucio
2009-11-15 17:26 ` Paul Lalonde
2009-11-15 22:25 ` ron minnich
2009-11-15 22:43 ` Bruce Ellis
2009-11-16 4:34 ` lucio
2009-11-16 10:11 ` Bruce Ellis
2009-11-16 4:28 ` lucio
2009-11-13 19:41 ` Andre Guenther
2009-11-15 17:55 ` lucio [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=2b34921287722b84f7f694b134d326e3@proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).