From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 8E28C138247 for ; Mon, 16 Dec 2013 15:39:24 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id AC983E0AF3; Mon, 16 Dec 2013 15:39:16 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id B908EE0ABA for ; Mon, 16 Dec 2013 15:39:15 +0000 (UTC) Received: from [192.168.1.100] (c-68-49-223-78.hsd1.md.comcast.net [68.49.223.78]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: mjo) by smtp.gentoo.org (Postfix) with ESMTPSA id E079233F11D for ; Mon, 16 Dec 2013 15:39:14 +0000 (UTC) Message-ID: <52AF1E7E.9030803@gentoo.org> Date: Mon, 16 Dec 2013 10:38:38 -0500 From: Michael Orlitzky User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Re: New global use flags: 3dnowext, mmxext, ssse3, sse4_1, avx, avx2 References: In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: 9753c124-1417-434f-a5ab-bef040d40839 X-Archives-Hash: 7b068ab92111c22497d4a83271b336b7 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?