public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: Alan Modra <amodra@bigpond.net.au>,
	soete.joel@tiscali.be, parisc-linux@parisc-linux.org,
	binutils@sources.redhat.com
Subject: Re: [parisc-linux] binutils 2.15?
Date: Thu, 01 Jul 2004 23:00:00 -0000	[thread overview]
Message-ID: <20040701225958.GL21264@devserv.devel.redhat.com> (raw)
In-Reply-To: <200407012249.i61MnikF010941@hiauly1.hia.nrc.ca>

On Thu, Jul 01, 2004 at 06:49:44PM -0400, John David Anglin wrote:
> The enclosed patch moves .plt back to where it was before Jakub's change
> when NO_SMALL_DATA isn't defined.  We don't define NO_SMALL_DATA on
> PA-RISC as we need support for .sbss and .sdata.
> 
> This fixes the regressions.  The alternatives look messy impacting
> both gcc and glibc.

I think you want a new variable to control that instead (set on just hppa,
not set on other arches).
There are many small data targets where you IMHO want .plt where it is ATM
(anything starting from .data onwards can be overwritten by buffer overflow,
backward data overflows are much less common),  and furthermore rewriting
all the ld/testsuite tests again takes a lot of time.

> 2004-07-01  John David Anglin  <dave.anglin@nrc-cnrc.gc.ca>
> 
> 	* scripttempl/elf.sc: Place PLT before GOT when NO_SMALL_DATA is not
> 	defined.
> 
> Index: scripttempl/elf.sc
> ===================================================================
> RCS file: /cvs/src/src/ld/scripttempl/elf.sc,v
> retrieving revision 1.45
> diff -u -3 -p -r1.45 elf.sc
> --- scripttempl/elf.sc	15 Jun 2004 16:39:17 -0000	1.45
> +++ scripttempl/elf.sc	1 Jul 2004 22:03:14 -0000
> @@ -358,7 +358,7 @@ cat <<EOF
>    ${RELOCATING+${DATA_SEGMENT_RELRO_END}}
>    ${NO_SMALL_DATA+${RELRO_NOW-${SEPARATE_GOTPLT-${GOT}}}}
>  
> -  ${DATA_PLT+${PLT}}
> +  ${NO_SMALL_DATA+${DATA_PLT+${PLT}}}
>  
>    .data         ${RELOCATING-0} :
>    {
> @@ -370,6 +370,7 @@ cat <<EOF
>    .data1        ${RELOCATING-0} : { *(.data1) }
>    ${WRITABLE_RODATA+${RODATA}}
>    ${OTHER_READWRITE_SECTIONS}
> +  ${NO_SMALL_DATA-${DATA_PLT+${PLT}}}
>    ${RELOCATING+${OTHER_GOT_SYMBOLS}}
>    ${NO_SMALL_DATA-${GOT}}
>    ${OTHER_GOT_SECTIONS}

	Jakub

  reply	other threads:[~2004-07-01 23:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <40BDA020000074B9@ocpmta3.freegates.net>
2004-06-14  4:09 ` John David Anglin
2004-06-14  5:39   ` Jakub Jelinek
2004-06-14 12:08     ` Alan Modra
2004-06-21 15:18       ` Carlos O'Donell
2004-06-28  3:25         ` John David Anglin
2004-07-01 22:50       ` John David Anglin
2004-07-01 23:00         ` Jakub Jelinek [this message]
2004-07-22 10:09           ` Joel Soete
     [not found] <20040702040316.GL21696@bubble.modra.org>
2004-07-05 20:18 ` John David Anglin
2004-07-05 20:34 ` John David Anglin

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=20040701225958.GL21264@devserv.devel.redhat.com \
    --to=jakub@redhat.com \
    --cc=amodra@bigpond.net.au \
    --cc=binutils@sources.redhat.com \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=parisc-linux@parisc-linux.org \
    --cc=soete.joel@tiscali.be \
    /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).