Re: Should .a library contains non-reallocatable code?

[Simon Richter <Simon.Richter@hogyros.de>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

Am 20.02.2015 um 13:36 schrieb Jakub Wilk:

> IMO the policy is overly strict and it should be relaxed.

Speaking of relaxing things: could this be solved with linker relaxations?

The compiler would need to generate both PIC and non-PIC code in this
case, and specify that the non-PIC code can substitute the PIC code
unless the required relocations cannot be performed. This is similar
to the normal use case for relaxations, where I would generate e.g.
two alternative jump instructions differing in offset length, and
instruct the linker to use the shorter form.

   Simon
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iJwEAQECAAYFAlTnhykACgkQ0sfeulffv7t9SQP/ciifpIJLcZcJh/rEM0+EnhmB
S9zs1n5xK7pJLXF7rQG1NCTUWXipm6Pgaul1SJRmaURkizd7to1d9h1XvJJGGLno
9awHZstfKyrr/ukpuu6CifGHzhgiMemZ7QvZRnLT1lZVAF2YGREc0daQDQRwVLNT
8BPQnm4VYsXKUYtlLhs=
=M4GR
-----END PGP SIGNATURE-----