From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13790 invoked by alias); 19 Nov 2014 23:40:39 -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 13726 invoked by uid 48); 19 Nov 2014 23:40:36 -0000 From: "egall at gwmail dot gwu.edu" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/49379] warning from linker: alignment lost for -ftree-vectorize optimization Date: Wed, 19 Nov 2014 23:40:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 4.7.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: egall at gwmail dot gwu.edu X-Bugzilla-Status: NEW X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: 2014-11/txt/msg02111.txt.bz2 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49379 Eric Gallager changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |egall at gwmail dot gwu.edu --- Comment #8 from Eric Gallager --- (In reply to Dominique d'Humieres from comment #3) > Confirmed on x86_64-apple-darwin10 > > @(#)PROGRAM:ld PROJECT:ld64-97.17 > llvm version 2.9svn, from Apple Clang 1.7 (build 77) > > and powerpc-apple-darwin9.8.0 > > @(#)PROGRAM:ld PROJECT:ld64-85.2.1 > It looks like Apple has removed the warning since then; searching opensource.apple.com for the warning string in the OP shows that the most recent time it appeared was around line 246 of ld64/ld64-127.2/src/ld/SymbolTable.cpp. Looking around the same place in my copy of the ld64-136 sources, the warning is now no longer anywhere to be found around there. Still, I suppose, though, if other linkers still print similar warnings, the underlying issue must still remain then...