From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-363119-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 27506 invoked by alias); 19 Jul 2011 16:58:17 -0000
Received: (qmail 27496 invoked by uid 22791); 19 Jul 2011 16:58:16 -0000
X-SWARE-Spam-Status: No, hits=-2.8 required=5.0	tests=ALL_TRUSTED,AWL,BAYES_00
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; Tue, 19 Jul 2011 16:57:59 +0000
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/45351] many unaligned accesses in libgomp tests
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ro at CeBiTec dot Uni-Bielefeld.DE
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ro at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 4.7.0
X-Bugzilla-Changed-Fields:
Message-ID: <bug-45351-4-1YggwlXHDn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-45351-4@http.gcc.gnu.org/bugzilla/>
References: <bug-45351-4@http.gcc.gnu.org/bugzilla/>
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
Date: Tue, 19 Jul 2011 16:58:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
X-SW-Source: 2011-07/txt/msg01603.txt.bz2

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

--- Comment #11 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> 2011-07-19 16:57:00 UTC ---
> Do struct alignment rules on Tru64 have an effect? Not that I
> looked-up/read the ABI details..

I had a look at `Calling Standard for Alpha Systems', and the rules
seemed as expected and straight-forward.

> But I'd be curious what this does:
>
> #include something
> #include stddef.h
>
>
> int main()
> {
> typedef struct { char a; sem_t b; } t1;
>  printf("%u %u\n", sizeof(t1), offsetof(t1, b));
>  return 0;
> }
>
>   5 or 6 or 8 or other?
>   and 1 or 2 or 4 or other?
>   If the alignment is really only 2, then I'd expect 6 and 2.

This is what I get, with both cc and gcc.

    Rainer