public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c/54266] New: atomic / sync preprocessor macros inconsistent with (does not reflect) functionality of atomic / sync support.
@ 2012-08-14 23:06 hp at gcc dot gnu.org
  0 siblings, 0 replies; only message in thread
From: hp at gcc dot gnu.org @ 2012-08-14 23:06 UTC (permalink / raw)
  To: gcc-bugs

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

             Bug #: 54266
           Summary: atomic / sync preprocessor macros inconsistent with
                    (does not reflect) functionality of atomic / sync
                    support.
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: hp@gcc.gnu.org
                CC: amacleod@redhat.com


The preprocessor macros defined in c-family/c-cppbuiltin.c:cpp_atomic_builtins
don't correctly reflect whether atomic builtins work (can be linked and
executed). They just check for presence of certain MD patterns, while library
calls are just as valid.

This PR is similar to PR54006, but just intended to track the issue of
usability of the preprocessor macros.  For example, the cas_int target; the
check_effective_target_cas_int function doesn't catch targets implementing
atomics by calling library functions because __GCC_HAVE_SYNC_COMPARE_AND_SWAP_2
and __GCC_HAVE_SYNC_COMPARE_AND_SWAP_4 are unusable for this purpose.  See also
the test-case in PR54261.


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2012-08-14 23:06 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-08-14 23:06 [Bug c/54266] New: atomic / sync preprocessor macros inconsistent with (does not reflect) functionality of atomic / sync support hp at gcc dot gnu.org

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).