public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug regression/37640]  New: Misuse of __sync_lock_test_and_set causes ICE
@ 2008-09-24 16:32 anton at samba dot org
  2008-09-24 19:56 ` [Bug target/37640] " pinskia at gcc dot gnu dot org
                   ` (6 more replies)
  0 siblings, 7 replies; 8+ messages in thread
From: anton at samba dot org @ 2008-09-24 16:32 UTC (permalink / raw)
  To: gcc-bugs

A gcc build from today (gcc version 4.4.0 20080924) gets an ICE on PowerPC when
building this (admittedly broken) code:

# gcc -m64 -O2 -c test.c

struct foo {
        int a;
        char lock;
};
struct foo *foo;

void testcase()
{
        __sync_lock_test_and_set(&(foo->lock), 0);
}

It compiles if building 32bit. Even so, I wonder if gcc should warn when the
variable is incompatible with __sync_* builtins.


-- 
           Summary: Misuse of __sync_lock_test_and_set causes ICE
           Product: gcc
           Version: 4.4.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: regression
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: anton at samba dot org
GCC target triplet: powerpc-linux


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


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

end of thread, other threads:[~2008-11-18 22:10 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-09-24 16:32 [Bug regression/37640] New: Misuse of __sync_lock_test_and_set causes ICE anton at samba dot org
2008-09-24 19:56 ` [Bug target/37640] " pinskia at gcc dot gnu dot org
2008-09-24 20:08 ` anton at samba dot org
2008-09-24 20:17 ` pinskia at gcc dot gnu dot org
2008-09-28 21:18 ` [Bug target/37640] __sync_lock_test_and_set on PPC64 " pinskia at gcc dot gnu dot org
2008-09-28 23:08 ` pinskia at gcc dot gnu dot org
2008-09-28 23:09 ` pinskia at gcc dot gnu dot org
2008-11-18 22:10 ` bje 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).