| 1 |
> > > > Why would flags like mmx, mmxext, sse, and sse2 be masked from mplayer |
| 2 |
> > > > for me? |
| 3 |
> > > > |
| 4 |
> > > > /etc/make.profile -> |
| 5 |
> > > > /usr/portage/profiles/default-linux/amd64/2006.1/desktop |
| 6 |
> > > |
| 7 |
> > > I'm not sure why the use flags are masked. |
| 8 |
> > |
| 9 |
> > Heh, and then I found it... |
| 10 |
> > |
| 11 |
> > http://bugs.gentoo.org/show_bug.cgi?id=104674 |
| 12 |
> > |
| 13 |
> |
| 14 |
> Several days ago the guys at gentoo-am64 mailing list explained to me |
| 15 |
> all these flags enable different CFLAGS optimizations which came as the |
| 16 |
> x86 architecture evolved during the years. When using amd64 the CFLAG |
| 17 |
> "-march amd64" enables all architecture specific functions in gcc. |
| 18 |
> Simply gcc knows this CPU supports these instuction sets. Further AMD64 |
| 19 |
> provides sse2 and the latest CPU models even sse3 which are superior to |
| 20 |
> mmx, 3dnow and the other flags mentioned in this thread. So there is |
| 21 |
> nothing wrong if these are hard disabled - gcc will take advantage of |
| 22 |
> the amd64 arch. without these flags beeng enabled. |
| 23 |
> Also I found this official article in the amd64 project site: |
| 24 |
> http://www.gentoo.org/doc/en/gentoo-amd64-faq.xml#cflags |
| 25 |
> |
| 26 |
> "Warning: You should never place -fPIC, -m32 or -m64 in your CFLAGS. |
| 27 |
> They are automatically added whenever they are needed. Please also note |
| 28 |
> that the -Os flag is currently not supported." |
| 29 |
|
| 30 |
I'm actually using -march=k8 in accordance with the Gentoo Handbook's |
| 31 |
recommendation. Should I be using -march=amd64? I have an AMD |
| 32 |
Sempron64 3000+ CPU. |
| 33 |
|
| 34 |
- Grant |
| 35 |
-- |
| 36 |
gentoo-user@g.o mailing list |
Archives