1 |
fredag 21 oktober 2011 15.25.54 skrev Duncan: |
2 |
> Mike Frysinger posted on Fri, 21 Oct 2011 08:13:22 -0400 as excerpted: |
3 |
> > On Thursday 20 October 2011 23:20:35 Duncan wrote: |
4 |
> >> Magnus G suggests possibly adding PIE to amd64, which is already PIC, |
5 |
> > |
6 |
> > this isn't quite right. amd64 shared objects (i.e. libraries) are PIC. |
7 |
> > the applications are not. |
8 |
> |
9 |
> Thanks for the correction. I knew the library think but supposed that |
10 |
> was the difference between PIC/PIE, the E/executable for executables |
11 |
> only, the more generic C/code for the feature applied to shared objects. |
12 |
> |
13 |
> Seems there's a bit more to it than that. Thanks again, I can look it up |
14 |
> now that I know to do so. |
15 |
> |
16 |
> > usually these packages are multimedia related. like ffmpeg iirc. so i |
17 |
> > think the impact is much greater than your estimate here. |
18 |
> |
19 |
I don't have any probs with ffmpeg. We disable the asm stuff only for x86 and |
20 |
not amd64 and that is the case on alot of the multimedia related packages. |
21 |
Most problem we have now is the packages in app-emulation |
22 |
|
23 |
> I figured mm, but also assumed strip-flags-like exceptions (probably |
24 |
> controlled via USE flag) for packages where the default was really |
25 |
> costly. But now that I think of it, implementing that as arch defaults |
26 |
> while allowing overrides isn't quite the simple matter it is for user-set |
27 |
> CFLAGS, etc, and strip-flags, etc. |
28 |
We allready use pic USE flag, filter-flags -fPIE or gcc-specs-pie to disable |
29 |
or do stuff so the package works. |
30 |
|
31 |
> |
32 |
> I assume it can still be done, but am not in a position to estimate |
33 |
> whether it'd be worth the cost to implement. |
34 |
> |
35 |
> >> What about x32, tho? Does it get PIC by default too |
36 |
> > |
37 |
> > x32 is same as x86_64 wrt PIC |
38 |
> |
39 |
> Good to know. Thanks. |
40 |
|
41 |
/Magnus |