Mike Frysinger <[EMAIL PROTECTED]> said:
> this is correct, a very good reason to fix TEXTRELs.  another good
> reason is that since the segment cannot be mapped readonly, the memory
> cannot be shared across multiple processes ... each will need to have
> its own copy, thus wasting what could be significant memory resources.

Sounds like something nice to do, but not something that should be _required_
for a package to be deemed stable.

> > The constant need to look up the address is what causes
> > the performance degredation.  The performance degredation however is of
> > no worry to us.
> 
> if by "constant" you mean "once everytime the code is loaded", then you
> are correct ... the relocations need to be rewritten everytime the image
> is loaded into memory by the dynamic loader (ldso), but after the first
> fixup, that's it, nothing else to be done.

Again, nice to fix, but does not seem necessary.

> working on it as i said ... i wish this e-mail could have been posted
> once i had more easier things to read :p

You are working on a policy, or just docs to explain the issues?  From what
was listed above, I'm not sure why we should require that people fix these
issues just to have a package deemed stable.

-- 
Mark Loeser   -   Gentoo Developer (cpp gcc-porting toolchain x86)
email         -   halcy0n AT gentoo DOT org
                  mark AT halcy0n DOT com
web           -   http://dev.gentoo.org/~halcy0n/
                  http://www.halcy0n.com

Attachment: pgpqnl9LWsDn7.pgp
Description: PGP signature

Reply via email to