From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: New global use flags: 3dnowext, mmxext, ssse3, sse4_1, avx, avx2
Date: Mon, 16 Dec 2013 10:38:38 -0500 [thread overview]
Message-ID: <52AF1E7E.9030803@gentoo.org> (raw)
In-Reply-To: <pan$cb35e$3a5ea0a9$d4cb01a2$aac922@cox.net>
On 12/16/2013 05:44 AM, Duncan wrote:
> Matt Turner posted on Sun, 15 Dec 2013 15:34:13 -0800 as excerpted:
>
>> sse3: Use the SSE3 instruction set (pni in cpuinfo)
>> ssse3: Use the SSSE3 instruction set
>
> I'd suggest a parenthetical on ssse3 as well, something like:
>
> ssse3: Use the SSSE3 instruction set (NOT sse3, three s)
>
> I know that confused me for awhile, and I tend to be reasonably literate
> (as a user, anyway) on this sort of thing,
Why not go all the way?
"Enable use of the SSSE3 instruction set (NOT sse3). This is needed by
projects which contain assembly code or which use certain compiler
intrinsics. It is not a replacement for CFLAGS and friends."
You can make a case for brevity, but how many times do you find yourself
(a) reading USE flag descriptions, and (b) thinking they're too long?
next prev parent reply other threads:[~2013-12-16 15:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-15 23:34 [gentoo-dev] New global use flags: 3dnowext, mmxext, ssse3, sse4_1, avx, avx2 Matt Turner
2013-12-16 0:20 ` Andreas K. Huettel
2013-12-16 0:30 ` Matt Turner
2013-12-16 1:13 ` Francesco R.
2013-12-16 12:07 ` Jeroen Roovers
2013-12-16 23:07 ` Rick "Zero_Chaos" Farina
2013-12-18 17:48 ` Jeroen Roovers
2013-12-16 10:44 ` [gentoo-dev] " Duncan
2013-12-16 15:38 ` Michael Orlitzky [this message]
2013-12-16 18:21 ` Alan McKinnon
2013-12-16 20:17 ` Michael Orlitzky
2013-12-16 20:48 ` Alan McKinnon
2013-12-18 18:49 ` Matt Turner
2013-12-19 12:11 ` [gentoo-dev] " Jan Matejka
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=52AF1E7E.9030803@gentoo.org \
--to=mjo@gentoo.org \
--cc=gentoo-dev@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