From: Volker Armin Hemmann <volkerarmin@googlemail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] USE="mmx mmxext sse sse2 ssse3 3dnow 3dnowext"
Date: Fri, 29 May 2009 08:55:46 +0200 [thread overview]
Message-ID: <200905290855.46136.volkerarmin@googlemail.com> (raw)
In-Reply-To: <871vq85vcf.fsf@newton.gmurray.org.uk>
On Freitag 29 Mai 2009, Graham Murray wrote:
> Stroller <stroller@stellar.eclipse.co.uk> writes:
> > But, surely "-march=" also instructs gcc to support the additional
> > instructions. Suggest you re-read Daniel's post that I was replying
> > to.
> >
> > What's the difference between supporting the "certain set of
> > instructions" with "-march=" and doing so with USEs?
> >
> > Or doesn't "-march=" support additional "certain sets of
> > instructions". What does it do, then?
>
> I am not sure,
>
> $ gcc -Q --help=target -march=core2
> The following options are target specific:
> -m128bit-long-double [disabled]
> -m32 [enabled]
> -m3dnow [disabled]
> -m3dnowa [disabled]
> -m64 [disabled]
> -m80387 [enabled]
> -m96bit-long-double [enabled]
> -mabm [disabled]
> -maccumulate-outgoing-args [disabled]
> -maes [disabled]
> -malign-double [disabled]
> -malign-functions=
> -malign-jumps=
> -malign-loops=
> -malign-stringops [enabled]
> -march= core2
> -masm=
> -mavx [disabled]
> -mbranch-cost=
> -mcld [disabled]
> -mcmodel=
> -mcx16 [disabled]
> -mfancy-math-387 [enabled]
> -mfma [disabled]
> -mforce-drap [disabled]
> -mfp-ret-in-387 [enabled]
> -mfpmath=
> -mfused-madd [enabled]
> -mglibc [enabled]
> -mhard-float [enabled]
> -mieee-fp [enabled]
> -mincoming-stack-boundary=
> -minline-all-stringops [disabled]
> -minline-stringops-dynamically [disabled]
> -mintel-syntax [disabled]
> -mlarge-data-threshold=
> -mmmx [disabled]
> -mms-bitfields [disabled]
> -mno-align-stringops [disabled]
> -mno-fancy-math-387 [disabled]
> -mno-fused-madd [disabled]
> -mno-push-args [disabled]
> -mno-red-zone [disabled]
> -mno-sse4 [enabled]
> -momit-leaf-frame-pointer [disabled]
> -mpc
> -mpclmul [disabled]
> -mpopcnt [disabled]
> -mpreferred-stack-boundary=
> -mpush-args [enabled]
> -mrecip [disabled]
> -mred-zone [enabled]
> -mregparm=
> -mrtd [disabled]
> -msahf [disabled]
> -msoft-float [disabled]
> -msse [disabled]
> -msse2 [disabled]
> -msse2avx [disabled]
> -msse3 [disabled]
> -msse4 [disabled]
> -msse4.1 [disabled]
> -msse4.2 [disabled]
> -msse4a [disabled]
> -msse5 [disabled]
> -msseregparm [disabled]
> -mssse3 [disabled]
> -mstack-arg-probe [disabled]
> -mstackrealign [enabled]
> -mstringop-strategy=
> -mtls-dialect=
> -mtls-direct-seg-refs [enabled]
> -mtune=
> -muclibc [disabled]
> -mveclibabi=
get this:
dev.gentoo.org/~dirtyepic/bin/analyze-x86
and let it run, for example:
/analyze-x86 /bin/gzip
Checking vendor_id string... AuthenticAMD 64
Disassembling /bin/gzip, please wait...
i486: 0 i586: 0 ppro: 36 mmx: 46 3dnow: 0 ext3dnow: 0 sse:
0 sse2: 4 sse3: 0
/bin/gzip will run on AMD Athlon64 or higher processor.
or this:
/analyze-x86 /bin/bash
Checking vendor_id string... AuthenticAMD 64
Disassembling /bin/bash, please wait...
i486: 0 i586: 0 ppro: 369 mmx: 876 3dnow: 0 ext3dnow: 0 sse:
120 sse2: 0 sse3: 0
/bin/bash will run on Pentium III (pentium3) or higher processor.
and march=k8-sse3 -msse3 -O2 -pipe were my flags. Seems that a lot of stuff
got turned on ;)
mplayer is even more 'interessting':
./analyze-x86 /usr/bin/mplayer
Checking vendor_id string... AuthenticAMD 64
Disassembling /usr/bin/mplayer, please wait...
i486: 3948 i586: 14 ppro: 7573 mmx: 164986 3dnow: 5331 ext3dnow: 768 sse:
31407 sse2: 27712 sse3: 51
This binary was found to contain the cpuid instruction.
It may be able to conditionally execute instructions if
they are supported on the host (i586+).
/usr/bin/mplayer will run on AMD Athlon64 w/ SSE3 or higher processor.
next prev parent reply other threads:[~2009-05-29 6:55 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-26 4:27 [gentoo-user] USE="mmx mmxext sse sse2 ssse3 3dnow 3dnowext" Stroller
2009-05-26 4:37 ` Adam Carter
2009-05-26 4:59 ` Volker Armin Hemmann
2009-05-26 4:37 ` Volker Armin Hemmann
2009-05-26 5:00 ` Stroller
2009-05-26 5:10 ` Volker Armin Hemmann
2009-05-26 6:15 ` Stroller
2009-05-26 6:27 ` Volker Armin Hemmann
2009-05-26 8:34 ` Stroller
2009-05-26 14:31 ` Daniel Iliev
2009-05-26 21:07 ` Stroller
2009-05-27 0:47 ` Daniel Iliev
2009-05-27 8:14 ` Stroller
2009-05-27 10:00 ` Daniel Iliev
2009-05-27 12:14 ` Stroller
2009-05-27 19:57 ` Wyatt Epp
2009-05-27 20:04 ` Volker Armin Hemmann
2009-05-27 20:09 ` Alan McKinnon
2009-05-27 20:40 ` Wyatt Epp
2009-05-27 20:47 ` Volker Armin Hemmann
2009-05-27 21:04 ` Mike Edenfield
2009-05-27 21:12 ` Alan McKinnon
2009-05-27 23:00 ` Adam Carter
2009-05-27 20:08 ` Ward Poelmans
2009-05-27 21:04 ` Mike Edenfield
2009-05-27 21:23 ` Arttu V.
2009-05-28 10:17 ` Daniel Iliev
2009-05-28 19:13 ` Stroller
2009-05-28 20:08 ` Ward Poelmans
2009-05-28 20:19 ` Stroller
2009-05-28 20:27 ` Ward Poelmans
2009-05-28 20:38 ` Stroller
2009-05-29 5:30 ` Graham Murray
2009-05-29 6:36 ` Volker Armin Hemmann
2009-05-29 6:55 ` Volker Armin Hemmann [this message]
2009-05-29 15:25 ` Mike Edenfield
2009-05-29 7:51 ` Neil Bothwick
2009-05-26 22:20 ` KH
2009-05-26 22:26 ` KH
2009-05-26 22:32 ` Alan McKinnon
2009-05-26 13:26 ` [gentoo-user] " James
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200905290855.46136.volkerarmin@googlemail.com \
--to=volkerarmin@googlemail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox