| 1 |
From what I can tell here, pic is nearly built in to amd64. It should |
| 2 |
be used by default on amd64 and I think it has to be explicitly |
| 3 |
disabled (ffmpeg). So, you can run -pic on all amd64 and get nearly |
| 4 |
the same result as +pic on amd64. |
| 5 |
|
| 6 |
-- Prometheanfire |
| 7 |
|
| 8 |
On Mon, Feb 28, 2011 at 15:39, Daniel Reidy <dubkat@×××××.com> wrote: |
| 9 |
> On Sun, Feb 27, 2011 at 5:58 PM, <pageexec@××××××××.hu> wrote: |
| 10 |
>> that's actually not the intended use of the PIC USE flag, we wanted it originally |
| 11 |
>> to enable configuring/compiling position independent code for packages where one |
| 12 |
>> wanted to make a tradeoff between speed/security (i think php was one such app, |
| 13 |
>> even without any hand written asm code). |
| 14 |
>> |
| 15 |
>> so with USE=pic you were supposed to get a textrel free, but potentially slower |
| 16 |
>> binary (partly because of the PIC overhead on i386 and partly because sometimes |
| 17 |
>> it meant using the C implementation of some algo instead of hand written asm). |
| 18 |
> |
| 19 |
> So if I understand this correctly, we should now be turning off PIC on |
| 20 |
> Gentoo-Hardened systems running on AMD64. What about the non-hardened |
| 21 |
> variety, such as my desktop, that is only running a "stock" version of |
| 22 |
> Gentoo Sources without hardened features? |
| 23 |
> |
| 24 |
> -dan |
| 25 |
> |
| 26 |
> |
Archives