public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.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
Date: Fri, 15 Oct 2010 05:40:00 -0000	[thread overview]
Message-ID: <20101015054000.6BD5QE9Az7UCyS1Gjeoe707jAgPDS1q2_yw1RkhZ6WQ@z> (raw)
In-Reply-To: <bug-46031-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46031

--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> 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.


  parent reply	other threads:[~2010-10-15  5:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-15  5:03 [Bug web/46031] New: " justin.lebar+bug at gmail dot com
2010-10-15  5:08 ` [Bug web/46031] " pinskia at gcc dot gnu.org
2010-10-15  5:30 ` justin.lebar+bug at gmail dot com
2010-10-15  5:40 ` pinskia at gcc dot gnu.org [this message]
2010-10-15  5:54 ` justin.lebar+bug at gmail dot com

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=20101015054000.6BD5QE9Az7UCyS1Gjeoe707jAgPDS1q2_yw1RkhZ6WQ@z \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).