public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Danny Backx <danny.backx@scarlet.be>
To: Kai Tietz <ktietz70@googlemail.com>
Cc: binutils <binutils@sourceware.org>
Subject: Re: binutils arm/PE issue causing failure on Windows Mobile 6.1+
Date: Tue, 08 Sep 2009 16:08:00 -0000	[thread overview]
Message-ID: <1252426230.6106.311.camel@pavilion> (raw)
In-Reply-To: <90baa01f0909061225he3c9d1aj658836e82c1255a8@mail.gmail.com>

On Sun, 2009-09-06 at 21:25 +0200, Kai Tietz wrote:
> 2009/9/6 Danny Backx <danny.backx@scarlet.be>:
> > Where can I find info on version 1 vs version 2 ?
>
> as far as I know, there is just some technical documentation in
> comments of ld's pe-dll.c about it. But I try to summarize where the
> difference are between those two different pseudo-relocation
> implementation - Dave if you think I missed here something, please
> comment, too.
>
> v1 is at the moment AFAIK default for cygwin and windows 32-bit
> targets. For 64-bit window target v2 is already default, as v1 isn't
> usable for it at all.

Thanks. Very interesting. I'm looking into that documentation.

Your explanation makes it look like we're waiting for someone to port v2
to the 32-bit targets.

Is that all there is to it, or are there more issues ?

	Danny
-- 
Danny Backx ; danny.backx - at - scarlet.be ; http://danny.backx.info

      reply	other threads:[~2009-09-08 16:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <393699.26635.qm@web59310.mail.re1.yahoo.com>
     [not found] ` <478d3d0651678598383b6001c8399cf8@mail.smartmobili.com>
     [not found]   ` <1252145077.6106.268.camel@pavilion>
2009-09-06 16:27     ` Danny Backx
2009-09-06 16:38       ` Kai Tietz
2009-09-06 18:51         ` Danny Backx
2009-09-06 19:25           ` Kai Tietz
2009-09-08 16:08             ` Danny Backx [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=1252426230.6106.311.camel@pavilion \
    --to=danny.backx@scarlet.be \
    --cc=binutils@sourceware.org \
    --cc=ktietz70@googlemail.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).