From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4830 invoked by alias); 6 Aug 2013 16:12:31 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 4722 invoked by uid 48); 6 Aug 2013 16:12:28 -0000 From: "bernd.edlinger at hotmail dot de" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/58041] Unaligned access to arrays in packed structure Date: Tue, 06 Aug 2013 16:12:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 4.9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: bernd.edlinger at hotmail dot de X-Bugzilla-Status: ASSIGNED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: jamborm at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2013-08/txt/msg00376.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58041 --- Comment #36 from Bernd Edlinger --- (In reply to Martin Jambor from comment #35) > (In reply to Bernd Edlinger from comment #34) > by the way the initializer > of "struct s a = " > seems to generate warnings at -Wall, because some > brackets are missing: > > changed that to > struct s a = {0,{{0,0},{0,0}}}; > > > but somehow I wonder what forced us to generate sse instructions here? > > when that same example works on a ARMv5 targe? > Strange, does the correct > initializer make the warning go away? > If so, I'll fix it in the testsuite in a moment. no that is just a different warning with -Wall, that one did not make the test case fail however. and in line 6 the "typedef struct S { V v; } P __attribute__((aligned (1)));" is superfluos too. hmm, maybe the problem is I should not say -msse in the first place. do you get the warning if you use -m32 -mno-sse ? what's funny about that warning, that it does not need to be enabled with -Wall like the other warning.