public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: New global use flags: 3dnowext, mmxext, ssse3, sse4_1, avx, avx2
Date: Mon, 16 Dec 2013 10:44:55 +0000 (UTC)	[thread overview]
Message-ID: <pan$cb35e$3a5ea0a9$d4cb01a2$aac922@cox.net> (raw)
In-Reply-To: CAEdQ38EtL0_ZnO9W8qsLi1WuKb1Aq8u96cJOpyvruHcwsdXf9Q@mail.gmail.com

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, so I'd not be surprised in the 
least if a lot of sse3 only folks end up enabling it in error, as I did.  
The explicit three-count pointer should help eliminate that sort of 
confusion.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman



  parent reply	other threads:[~2013-12-16 10:45 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 ` Duncan [this message]
2013-12-16 15:38   ` [gentoo-dev] " Michael Orlitzky
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='pan$cb35e$3a5ea0a9$d4cb01a2$aac922@cox.net' \
    --to=1i5t5.duncan@cox.net \
    --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