public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Daney <ddaney@avtrex.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
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: Mon, 13 Aug 2007 18:19:00 -0000	[thread overview]
Message-ID: <46C0A09D.1060309@avtrex.com> (raw)
In-Reply-To: <Pine.LNX.4.64N.0708131549050.2722@blysk.ds.pg.gda.pl>

Maciej W. Rozycki wrote:
> David,
> 
>  While integrating into 4.1.2 I had a brief look over your patch again 
> over the weekend and I have got two minor points:
> 
> 1. You use "unsigned" rather than "unsigned int", which makes your code 
>    look a little bit too K&Rish.

Prior art in src/mips/ffi.c has it both ways.  The patch very much 
carries on this tradition.

> 
> 2. Given the coverage FFI_MIPS_N32 should probably be renamed to 
>    FFI_MIPS_NEWABI as it is now somewhat confusing.

On the principle that a patch should only make changes necessary to 
implement its main goal, I left this as it was.

I would not oppose patches that address either of these issues.

> 
> And last but not least, with your changes there is now no difference 
> between Linux and IRIX anymore, so it may be worth unifying the MIPS 
> target like the others; it seems to be the only oddball.
> 
> 2007-08-13  Maciej W. Rozycki  <macro@linux-mips.org>
> 
> 	* Makefile.am: Unify MIPS_IRIX and MIPS_LINUX into MIPS.
> 	* configure.ac: Likewise.
> 	* Makefile.in: Regenerate.
> 	* configure: Regenerate.
> 
>  OK to apply?

I cannot approve the patch, but if it was tested on both Irix and 
mips64-linux I think it is a good idea.

Thanks,
David Daney

  reply	other threads:[~2007-08-13 18:19 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
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 [this message]
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=46C0A09D.1060309@avtrex.com \
    --to=ddaney@avtrex.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=java-patches@gcc.gnu.org \
    --cc=macro@linux-mips.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).