public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Charles Wilson <cwilson@ece.gatech.edu>
To: egor duda <binutils@sources.redhat.com>
Cc: cygwin-apps@sources.redhat.com
Subject: Re: --enable-auto-import extension
Date: Wed, 03 Jul 2002 12:05:00 -0000	[thread overview]
Message-ID: <3D234258.9050008@ece.gatech.edu> (raw)
In-Reply-To: <903891375.20020702193614@logos-m.ru>

egor duda wrote:


> Someone suggested that one can do 'cmp -i 150 old.dll new.dll', or
> whatever offset timestamp is located at.
> 
> Ok, i've finalized patch and test. I suppose i have a copyright
> assignment with FSF for this changes to get incorporated into official
> sources. As far as i understand, i have to get an assignment form from
> binutils maintainer, right? 


The new version looks good to me; I built and ran your test without 
problems.  I do have a suggestion for later, when 
--enable-runtime-pseudo-reloc is made the default: in pe-dll.c (around 
line 2209) change

if (pe_dll_extra_pe_debug)
   printf ("creating runtime pseudo-reloc entry for %s (addend=%d)\n",
      fixup_name, addend);

to

if (link_info.pei386_runtime_pseudo_reloc == -1)
   info_msg (_("creating runtime pseudo-reloc entry for %s (addend=%d)\n"),
      fixup_name, addend);

So that if pseudo_reloc is implicitly enabled, print messages for each 
psuedo-reloc entry (but not all that other pe_dll_extra_pe_debug stuff). 
  It's not a warning, but its info the user probably needs to know if he 
didn't explicitly say "--enable-runtime-pseudo-reloc".

But that's not important until AFTER pseudo-reloc is made the default.

The business with fork() and -DNO_RUNTIME_PSEUDO_RELOC_SUPPORT stuff in 
your example is a bit confusing -- do you have some pending patches to 
cygwin1.dll?

--Chuck


  parent reply	other threads:[~2002-07-03 18:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-28  3:19 egor duda
2002-06-28 18:08 ` Charles Wilson
2002-06-30 23:47   ` egor duda
2002-07-01 14:28     ` Charles Wilson
2002-07-02  8:39       ` egor duda
2002-07-02  9:31         ` Christopher Faylor
2002-07-03  2:21         ` egor duda
2002-07-03 12:05         ` Charles Wilson [this message]
2002-07-04  3:43           ` egor duda
2002-08-15 10:49             ` Christopher Faylor
2002-08-15 23:21               ` egor duda
2002-07-07 18:20   ` David A. Cobb
2002-11-11 18:01 Charles Wilson
2002-11-14 10:07 ` Nick Clifton
2002-11-15  5:35   ` egor duda

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=3D234258.9050008@ece.gatech.edu \
    --to=cwilson@ece.gatech.edu \
    --cc=binutils@sources.redhat.com \
    --cc=cygwin-apps@sources.redhat.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).