From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: David Daney <ddaney@avtrex.com>
Cc: Richard Sandiford <richard@codesourcery.com>,
GCJ-patches <java-patches@gcc.gnu.org>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [Patch] libffi: Add MIPS64 support.
Date: Fri, 10 Aug 2007 10:58:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64N.0708101150260.1469@blysk.ds.pg.gda.pl> (raw)
In-Reply-To: <46BB4F54.108@avtrex.com>
On Thu, 9 Aug 2007, David Daney wrote:
> Indeed. I will fix it before committing.
And thanks for your effort BTW -- it looks much better than the hack I
developed a while ago. I will put your changes into my n64 GCC package
and see how it behaves.
Also -- if anybody is interested in MIPS new ABI changes relevant to GCJ,
then I have some patches which I was able to bring up to version 4.1.2.
Unfortunately I have too many other tasks on my head now, so I may not be
able to port them up to the current version any time soon, but I would be
happy if they proved useful for someone or found their way up to the trunk
eventually. I have some Ada patches too. ;-)
Maciej
next prev parent reply other threads:[~2007-08-10 10:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-09 5:01 David Daney
2007-08-09 9:58 ` Richard Sandiford
2007-08-09 15:50 ` David Daney
2007-08-09 15:59 ` Richard Sandiford
2007-08-09 17:28 ` Maciej W. Rozycki
2007-08-09 17:31 ` David Daney
2007-08-10 10:58 ` Maciej W. Rozycki [this message]
2007-08-10 15:26 ` David Daney
2007-08-10 17:22 ` Maciej W. Rozycki
2007-08-11 5:43 ` David Daney
2007-08-13 17:56 ` Maciej W. Rozycki
2007-08-13 18:19 ` David Daney
2007-08-13 20:51 ` Tom Tromey
2007-08-14 11:53 ` Maciej W. Rozycki
2007-08-15 6:40 ` David Daney
2007-08-17 20:23 ` Tom Tromey
2007-09-03 18:09 ` Maciej W. Rozycki
2007-08-13 18:38 ` Andreas Schwab
2007-08-10 15:49 ` David Daney
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=Pine.LNX.4.64N.0708101150260.1469@blysk.ds.pg.gda.pl \
--to=macro@linux-mips.org \
--cc=ddaney@avtrex.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=java-patches@gcc.gnu.org \
--cc=richard@codesourcery.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).