public inbox for java-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Timothy Wall <twalljava@dev.java.net>
To: NightStrike <nightstrike@gmail.com>
Cc: Dave Korn <dave.korn.cygwin@googlemail.com>,
	Andrew Haley <aph@redhat.com>,
	 gcc-patches@gcc.gnu.org, java-patches@gcc.gnu.org,
	 libffi-discuss@sourceware.org
Subject: Re: [PATCH] win64 support for libffi (2/2)
Date: Mon, 18 May 2009 18:09:00 -0000	[thread overview]
Message-ID: <2AB07EC8-8D86-4F74-8763-0F5379FC3077@dev.java.net> (raw)
In-Reply-To: <b609cb3b0905181059y1c75cff5k971eba40ad3d25f5@mail.gmail.com>

There seem to be some win32 patches in sourceware libffi that aren't  
in gcc/libffi.  Probably some other things as well.

On May 18, 2009, at 1:59 PM, NightStrike wrote:

> On Mon, May 18, 2009 at 2:00 PM, Dave Korn
> <dave.korn.cygwin@googlemail.com> wrote:
>> Andrew Haley wrote:
>>> Dave Korn wrote:
>>>> Andrew Haley wrote:
>>>>
>>>>> The libffi ABI has changed?  Are you sure?
>>>>   No, I'm not clear, I'm repeating something I was told second- 
>>>> hand:
>>>>
>>>> http://www.cygwin.com/ml/cygwin-apps/2009-02/msg00051.html
>>>>
>>>>   Maybe I just meant that the API has changed, not the ABI?
>>>
>>> Neither have changed AFAIAA.  There are some updates and fixes in  
>>> gcc
>>> that are not yet in upstream libffi.
>>
>>  Ok, this is what I mean:
>>
>> admin@ubik /tmp/libffi/upstream
>> $ tail -2 /tmp/libffi/upstream/libffi-3.0.8/libtool-version
>> # CURRENT:REVISION:AGE
>> 5:9:0
>>
>> admin@ubik /tmp/libffi/upstream
>> $ tail -2 /gnu/gcc/gcc/libffi/libtool-version
>> # CURRENT:REVISION:AGE
>> 4:1:0
>
> Maybe it needs to be merged in both directions.

  reply	other threads:[~2009-05-18 18:09 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <635C3243-B89E-460E-9C0F-209308D89729@dev.java.net>
     [not found] ` <b609cb3b0905171605tc6a10b7u683c43a99f97382f@mail.gmail.com>
     [not found]   ` <4A109F74.6060108@gmail.com>
2009-05-17 23:49     ` Timothy Wall
2009-05-17 23:51       ` NightStrike
2009-05-18  9:36       ` Andrew Haley
2009-05-18  9:41         ` Richard Guenther
2009-05-18 10:16           ` Andrew Haley
2009-05-18 14:46         ` Dave Korn
2009-05-18 14:59           ` Andrew Haley
2009-05-18 15:06             ` Dave Korn
2009-05-18 17:48             ` Dave Korn
2009-05-18 17:59               ` NightStrike
2009-05-18 18:09                 ` Timothy Wall [this message]
2009-05-18 18:41                   ` Andrew Haley
2009-05-18 19:00                     ` Timothy Wall
2009-05-19  9:16                       ` Andrew Haley
2009-05-19 12:13                         ` Dave Korn
2009-05-21 21:08                         ` NightStrike
2009-05-22  8:54                           ` Andrew Haley
2009-05-22 12:01                             ` Dave Korn
2009-05-22 13:01                               ` Andrew Haley
2009-05-22 13:53                                 ` Dave Korn
2009-05-22 14:02                                   ` Andrew Haley
2009-05-22 14:16                                     ` Dave Korn
2009-05-22 14:42                                   ` Timothy Wall
2009-05-18 10:12 ` Andrew Haley
2009-05-18 12:26   ` Timothy Wall
2009-05-18 14:37     ` Andrew Haley
2009-05-18 15:31       ` Timothy Wall
2009-05-18 18:06       ` Timothy Wall

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=2AB07EC8-8D86-4F74-8763-0F5379FC3077@dev.java.net \
    --to=twalljava@dev.java.net \
    --cc=aph@redhat.com \
    --cc=dave.korn.cygwin@googlemail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=java-patches@gcc.gnu.org \
    --cc=libffi-discuss@sourceware.org \
    --cc=nightstrike@gmail.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).