public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug treelang/41639]  New: synchronisation primitives take unsigned as input and output values.
@ 2009-10-09  7:06 chrbr at gcc dot gnu dot org
  2009-10-09  7:12 ` [Bug treelang/41639] " chrbr at gcc dot gnu dot org
  2010-07-20 22:21 ` [Bug middle-end/41639] " steven at gcc dot gnu dot org
  0 siblings, 2 replies; 3+ messages in thread
From: chrbr at gcc dot gnu dot org @ 2009-10-09  7:06 UTC (permalink / raw)
  To: gcc-bugs

Current implementation of the synchronization builtins in gcc (from
http://software.intel.com/sites/products/documentation/hpc/compilerpro/en-us/cpp/lin/compiler_c/intref_cls/common/intref_itanium_synchro_prim.htm)
describe <type> as unsigned. although it is stated as "<type> is either a
32-bit or 64-bit integer"

consequently, testsuite tests such as sync-2.c:

if (__sync_sub_and_fetch(AI+13, 12) != (char)-12)
    abort ();

might fail. (unless the target/runtime dependant primitive implementation
artificially change the return type).


-- 
           Summary: synchronisation primitives take unsigned as input and
                    output values.
           Product: gcc
           Version: 4.5.0
            Status: UNCONFIRMED
          Severity: trivial
          Priority: P3
         Component: treelang
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: chrbr at gcc dot gnu dot org


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


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2010-07-20 22:21 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-10-09  7:06 [Bug treelang/41639] New: synchronisation primitives take unsigned as input and output values chrbr at gcc dot gnu dot org
2009-10-09  7:12 ` [Bug treelang/41639] " chrbr at gcc dot gnu dot org
2010-07-20 22:21 ` [Bug middle-end/41639] " steven at gcc dot gnu dot 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).