From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27253 invoked by alias); 15 Oct 2010 05:40:09 -0000 Received: (qmail 27243 invoked by uid 22791); 15 Oct 2010 05:40:07 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00,MISSING_MID X-Spam-Check-By: sourceware.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 15 Oct 2010 05:40:04 +0000 From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug web/46031] Atomic Builtins page should indicate that 16-byte compare-and-swap is available with -mcex16 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: web X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: pinskia at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Date: Fri, 15 Oct 2010 05:40:00 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2010-10/txt/msg01265.txt.bz2 Message-ID: <20101015054000.6BD5QE9Az7UCyS1Gjeoe707jAgPDS1q2_yw1RkhZ6WQ@z> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46031 --- Comment #3 from Andrew Pinski 2010-10-15 05:39:53 UTC --- Actually it says the target processors might not include all of the builtins. What is a target processor is up to each target and likewise on how to change the processor. This should allow you to read the target options for how to change the processor GCC is targeting. This is the same issue as -march=i386 does not support any of them vs -march=i686 supports the majority of them. The x86 specific options explicitly references the atomic builtins. Again I don't think we should reference target specific options in the generic part of the manual. Doing that makes the manual even more confusing. Maybe adding the following sentence will help: Each target defines how a specific processor is selected, see the target options pages on how to select the specific processor.