public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Jack Howarth <howarth@nitro.med.uc.edu>
Cc: binutils@sources.redhat.com
Subject: Re: -z combreloc
Date: Sat, 13 Oct 2001 13:20:00 -0000	[thread overview]
Message-ID: <20011013222328.A666@sunsite.ms.mff.cuni.cz> (raw)
In-Reply-To: <200110131746.NAA32978@nitro.msbb.uc.edu>

On Sat, Oct 13, 2001 at 01:46:12PM -0400, Jack Howarth wrote:
> Hello,
>    Debian is preparing to enable -z combreloc
> in their binutils 2.11.92.0.5 packages. On Debian
> ppc sid the -z combreloc enabled binutils builds
> fine and passes all of make check without problems.
> This is enabling -z combreloc with the simple patch...

We are using it in Red Hat binutils too for some time already, but only
apply it on elf platforms which are known to work with it.
Particularly, only ELF backends for which DT_TEXTREL handling has been
updated can have this on, which I think is not all yet (plus on mips the
separate .rel.dyn handling should be killed and use the common code).

> 2001-09-28  Ulrich Drepper  <drepper@redhat.com>
> 
> 	* elf/elf.h: Define SHF_GROUP and SHF_TLS.
> 
> ...are there any changes in glibc cvs since then with
> essential fixes for -z combreloc to work properly on
> any arches?

Why in glibc? SHF_GROUP is for ET_REL objects only as ELF standard sais, so
glibc has nothing to do with SHF_GROUP.
With -z combreloc, there are no changes needed in glibc, everything will
work as it used to, just when glibc knows about DT_REL*COUNT and has the one
entry lookup cache, it will make program startup faster.
Current glibc 2.2.4 has all this in.

> 3) Lastly, if one builds binaries on a machine with
> a binutils installed with -z combreloc enabled and
> transfers this to a machine with an older binutils
> with -z combreloc disabled...should we expect any
> backward compatibility issues in running these? 

Nope. As dynamic linker doesn't care about section table, the only change
visible to ld.so with -z combreloc and -z nocombreloc is that relocations
are sorted differently. But ld.so doesn't care about their ordering (well,
with -z nocombreloc e.g. .rel*.got is completely unsorted).

	Jakub

  parent reply	other threads:[~2001-10-13 13:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-13 10:47 Jack Howarth
2001-10-13 12:25 ` Andrew Cagney
2001-10-13 13:20 ` Jakub Jelinek [this message]
2001-10-13 13:15 Jack Howarth
2001-10-13 13:32 ` Jakub Jelinek
2001-10-13 13:53 ` Andrew Cagney
2001-10-13 15:30   ` Christopher C. Chimelis
2001-10-13 17:58     ` Andrew Cagney
2001-10-13 18:38 Jack Howarth
2001-10-13 19:01 ` Andrew Cagney
2001-10-13 19:14   ` Christopher C. Chimelis
2001-10-13 20:12 ` Andrew Cagney
2001-10-14  8:29   ` Daniel Jacobowitz
2001-10-14  8:46     ` Andrew Cagney

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=20011013222328.A666@sunsite.ms.mff.cuni.cz \
    --to=jakub@redhat.com \
    --cc=binutils@sources.redhat.com \
    --cc=howarth@nitro.med.uc.edu \
    /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).