Powerpc64 does not generate copy relocation for shared library variable

[kamlesh kumar]

Ok, thanks for the clarification.

On Tue, Jul 30, 2019, 11:53 AM Alan Modra <amodra@gmail.com> wrote:

> On Tue, Jul 30, 2019 at 10:47:32AM +0530, kamlesh kumar wrote:
> > Hi Alan,
> > I was expecting same behavior from ppc64 as on ppc32.
> > excerpt from
> >
> https://docs.oracle.com/cd/E19120-01/open.solaris/819-0690/chapter4-84604/index.html
> >
> > Dynamic executables, however, are generally not created from
> > position-independent code.
> > Any references to external data they make can seemingly only be achieved
> at
> > runtime by modifying the code that makes the reference.
>
> Right, but ppc64 does generate PIC.
>
> > Modifying a read-only text segment is to be avoided. The *copy*
> relocation
> > technique can solve this reference.
>
> Thus generally doesn't need copies of shared library variables in
> .dynbss.
>
> --
> Alan Modra
> Australia Development Lab, IBM
>