public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "nenad at intrepid dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/49379] New: warning from Mac OS X linker alignment lost for -ftree-vectorize optimization Date: Sun, 12 Jun 2011 02:25:00 -0000 [thread overview] Message-ID: <bug-49379-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49379 Summary: warning from Mac OS X linker alignment lost for -ftree-vectorize optimization Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassigned@gcc.gnu.org ReportedBy: nenad@intrepid.com While running some tests on Mac OS X 10.6.7 I ran into the following warning from the linker: ld: warning: alignment lost in merging tentative definition _u_th_arr Test links without the warning if -fno-tree-vectorize option is provided when compiling the source. I didn't have a chance to verify that executable is correct as my test is hanging - there might be multiple reasons for it. Linker is: @(#)PROGRAM:ld PROJECT:ld64-123.2 llvm version 2.9svn, from Apple Clang 2.0 (build 139) I am attaching a small test program that I checked out against the snapshot of the compiler 4.7.0 20110604. Here is the output of the compile/link process: + snapshot/gcc/xgcc -B../bld/packed-opt/gcc/ -v Reading specs from ../bld/packed-opt/gcc/specs COLLECT_GCC=snapshot/gcc/xgcc COLLECT_LTO_WRAPPER=../bld/packed-opt/gcc/lto-wrapper Target: x86_64-apple-darwin10.7.4 Configured with: ../../src/gcc-4.7-20110604/configure --disable-bootstrap Thread model: posix gcc version 4.7.0 20110604 (experimental) (GCC) + snapshot/gcc/xgcc -B../bld/packed-opt/gcc/ -I. -O3 -c a.c + snapshot/gcc/xgcc -B../bld/packed-opt/gcc/ -I. -O3 -c b.c + snapshot/gcc/xgcc -B../bld/packed-opt/gcc/ -o a -O3 a.o b.o ld: warning: alignment lost in merging tentative definition _u_th_arr + snapshot/gcc/xgcc -B../bld/packed-opt/gcc/ -I. -O3 -fno-tree-vectorize -c a.c + snapshot/gcc/xgcc -B../bld/packed-opt/gcc/ -I. -O3 -fno-tree-vectorize -c b.c + snapshot/gcc/xgcc -B../bld/packed-opt/gcc/ -o a -O3 a.o b.o
next reply other threads:[~2011-06-12 2:25 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-06-12 2:25 nenad at intrepid dot com [this message] 2011-06-12 2:26 ` [Bug c/49379] " nenad at intrepid dot com 2011-06-12 11:43 ` rguenth at gcc dot gnu.org 2011-06-12 12:44 ` dominiq at lps dot ens.fr 2011-06-12 13:07 ` gary at intrepid dot com 2011-06-29 4:20 ` PHHargrove at lbl dot gov 2011-06-29 5:28 ` PHHargrove at lbl dot gov 2011-06-29 17:08 ` d.g.gorbachev at gmail dot com 2014-11-19 23:40 ` [Bug tree-optimization/49379] warning from linker: " egall at gwmail dot gwu.edu
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-49379-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).