public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: binutils@sourceware.org, Kai Tietz <Kai.Tietz@onevision.com>
Subject: Re: PING: patch: PR-4877 testsuite fix for secreloc32 x86_64
Date: Mon, 06 Aug 2007 12:19:00 -0000	[thread overview]
Message-ID: <20070806121948.GB21221@ednor.casa.cgf.cx> (raw)
In-Reply-To: <OF75D969A1.1D97A13D-ONC125732F.0041864A-C125732F.0041B374@onevision.de>

On Mon, Aug 06, 2007 at 01:57:37PM +0200, Kai Tietz wrote:
>Hi Christopher,
>
>> On Mon, Aug 06, 2007 at 09:34:55AM +0200, Kai Tietz wrote:
>> >Hi,
>> >
>> >this patch will fix the problem on secreloc32 tests for x86_64-mingw32. 
>
>> >For this target the ctor/dtor elements are 8 bytes long. This caused 
>the 
>> >FAIL.
>> >
>> >See bug-report: http://sourceware.org/bugzilla/show_bug.cgi?id=4877
>> >
>> >I tested this patch for x86_64-pc-mingw32 test-suite without any 
>> >regressions.
>> >
>> >ChangeLog for ld/testsuite:
>> >
>> >2007-08-02  Kai Tietz   <kai.tietz@onevision.com>
>> >
>> >        * ld-pe/pe.exp: special diff file for x86_64-mingw target.
>> >        * ld-pe/secrel_64.d: New.
>> 
>> Is there some reason why this wouldn't work under a potential
>> x86_64-cygwin target?  I haven't been paying enough attention to this
>> issue but it seems like whatever machinery works for mingw should also
>> work for cygwin eventually.
>
>If there would be a crt1 for cygwin, I am certain that it would work
>for x86_64-cygwin too.

Cygwin does have similar crt* mechanisms to every other platform out
there.  I'm not asking you to implement anything here but could you
maybe just keep cygwin in mind when making patches like this and not
just default to "mingw"?

cgf

  reply	other threads:[~2007-08-06 12:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-06  7:35 Kai Tietz
2007-08-06 11:33 ` Christopher Faylor
2007-08-06 11:58   ` Kai Tietz
2007-08-06 12:19     ` Christopher Faylor [this message]
2007-08-06 13:52       ` Kai Tietz
2007-08-06 14:44 ` Nick Clifton

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=20070806121948.GB21221@ednor.casa.cgf.cx \
    --to=cgf-use-the-mailinglist-please@sourceware.org \
    --cc=Kai.Tietz@onevision.com \
    --cc=binutils@sourceware.org \
    /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).