qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Aurelien Jarno <aurelien@aurel32.net>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] sparc-linux-user: Fix missing symbols in .rel/.rela.plt sections
Date: Sat, 7 Jan 2012 22:01:09 +0100	[thread overview]
Message-ID: <20120107210108.GC20942@hall.aurel32.net> (raw)
In-Reply-To: <CAAu8pHu44WYiTe=TzGL=z02rHBaJYUT3xtXaqJ13DWV61qF4AA@mail.gmail.com>

On Sat, Jan 07, 2012 at 08:36:12PM +0000, Blue Swirl wrote:
> On Sat, Jan 7, 2012 at 20:16, Aurelien Jarno <aurelien@aurel32.net> wrote:
> > Fix .rel.plt sections in the output to not only include .rel.plt
> > sections from the input but also the .rel.iplt sections and to define
> > the hidden symbols __rel_iplt_start and __rel_iplt_end around
> > .rel.iplt as otherwise we get undefined references to these when
> > linking statically to a multiarch enabled libc (using STT_GNU_IFUNC).
> >
> > Blue Swirl <blauwirbel@gmail.com>
> > Signed-off-by: Aurelien Jarno <aurelien@aurel32.net>
> > ---
> >  sparc.ld |   16 ++++++++++++++--
> >  1 files changed, 14 insertions(+), 2 deletions(-)
> >
> > diff --git a/sparc.ld b/sparc.ld
> > index 56efe34..e52c3d2 100644
> > --- a/sparc.ld
> > +++ b/sparc.ld
> > @@ -37,8 +37,20 @@ SECTIONS
> >   .rela.fini     : { *(.rela.fini)      }
> >   .rel.bss       : { *(.rel.bss)                }
> >   .rela.bss      : { *(.rela.bss)               }
> > -  .rel.plt       : { *(.rel.plt)                }
> > -  .rela.plt      : { *(.rela.plt)               }
> > +  .rel.plt      :
> > +  {
> > +    *(.rel.plt)
> > +    PROVIDE_HIDDEN (__rel_iplt_start = .);
> > +    *(.rel.iplt)
> > +    PROVIDE_HIDDEN (__rel_iplt_end = .);
> > +  }
> > +  .rela.plt       :
> > +  {
> > +    *(.rela.plt)
> > +    PROVIDE_HIDDEN (__rela_iplt_start = .);
> > +    *(.rela.iplt)
> > +    PROVIDE_HIDDEN (__rela_iplt_end = .);
> > +  }
> 
> PROVIDE_HIDDEN etc. were removed by
> 8733f6093c2b77502e7228503fc22024e51599b8 in order to support BSDs with
> older binutils (2.15). Maybe the ld scripts should be generated from a
> source file for example with CPP, so these lines could be tweaked.
> 

It seems this patch was in my local tree for too long, and it seems I
should have updated it before sending it...

Other architectures are now using PROVIDE instead of PROVIDE_HIDDEN for 
__rel{a,}_iplt_{start,end}, so I guess the same can be done for sparc and
ppc. I am going to do a test build to check that, and I'll come with a
new patch if it works.

-- 
Aurelien Jarno	                        GPG: 1024D/F1BCDB73
aurelien@aurel32.net                 http://www.aurel32.net

  reply	other threads:[~2012-01-07 21:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-07 20:16 [Qemu-devel] [PATCH] sparc-linux-user: Fix missing symbols in .rel/.rela.plt sections Aurelien Jarno
2012-01-07 20:36 ` Blue Swirl
2012-01-07 21:01   ` Aurelien Jarno [this message]
2012-01-10 17:38     ` Aurelien Jarno
2012-01-21 18:42       ` Blue Swirl
2013-04-06  6:08       ` [Qemu-devel] " Michael Tokarev
2013-05-08  7:18         ` Michael Tokarev
2013-05-09 17:56           ` Blue Swirl
2013-05-19 12:58             ` Aurelien Jarno
2013-05-19 14:51               ` Michael Tokarev

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=20120107210108.GC20942@hall.aurel32.net \
    --to=aurelien@aurel32.net \
    --cc=blauwirbel@gmail.com \
    --cc=qemu-devel@nongnu.org \
    /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 NNTP newsgroup(s).