public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Richard Earnshaw <rearnsha@gcc.gnu.org>
To: "Peter S. Mazinger" <ps.m@gmx.net>
Cc: binutils@sourceware.org
Subject: Re: elf32-arm.c corrections
Date: Mon, 04 Apr 2005 13:45:00 -0000	[thread overview]
Message-ID: <1112622331.20824.20.camel@pc960.cambridge.arm.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0503200200320.5758-300000@lnx.bridge.intra>

On Sun, 2005-03-20 at 01:15, Peter S. Mazinger wrote:
> Hello!
> 
> add_dynamic_entry: changes !info->shared to info->executable (PIE)
> corrects typo, and syncs up with other archs (some others could do the 
> same). For !relocs the hole part would be omitted, probably some speed gain.
> 
> Should the other patch (*3) for allocate_dynrelocs be applied (as done for 
> ppc32)?
> 
> Why is ELIMINATE_COPY_RELOCS not used for arm?
> 
> Thanks, Peter
> 
> Please cc to me, 

Sorry for the delay replying, I've been snowed under with other work of
late.

I think this is probably OK, but it's hard to be sure because you
haven't followed all the procedures.  When submitting a patch you need
to do all of the following (as a minimum):

1) Explain what you are trying to do.  Is this a bug that you've found?
If so, provide a testcase.  Is it an optimization?  If so, why is the
existing code non-optimal.  Try to avoid diving in with too much detail.
2) Describe the patch (you've done that, though it could be a little
clearer).
3) Provide a ChangeLog entry describing the mechanics of the patch
(functions that have been changed and how).
4) Provide a patch produced with 'diff -p' or 'diff -up' format (the -p
option is essential so that I can see which functions are being changed
from the patch).
5) State which configurations you've tested the patch on.

Please can you supply the additional information.

R.

  parent reply	other threads:[~2005-04-04 13:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-20  6:08 Peter S. Mazinger
2005-03-20 13:19 ` Daniel Jacobowitz
2005-03-20 15:39   ` Peter S. Mazinger
2005-03-20 19:45     ` Daniel Jacobowitz
2005-03-27 22:57       ` Peter S. Mazinger
2005-03-27 23:56         ` Daniel Jacobowitz
2005-03-28  1:58           ` Peter S. Mazinger
2005-03-29 22:05             ` Nick Clifton
2005-04-04 13:45 ` Richard Earnshaw [this message]
2005-04-04 14:27   ` Peter S. Mazinger
2005-04-04 14:41     ` Richard Earnshaw

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=1112622331.20824.20.camel@pc960.cambridge.arm.com \
    --to=rearnsha@gcc.gnu.org \
    --cc=binutils@sourceware.org \
    --cc=ps.m@gmx.net \
    /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).