public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "egall at gwmail dot gwu.edu" <gcc-bugzilla@gcc.gnu.org>
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 [thread overview]
Message-ID: <bug-49379-4-uriUmA1kIm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49379-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49379
Eric Gallager <egall at gwmail dot gwu.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |egall at gwmail dot gwu.edu
--- Comment #8 from Eric Gallager <egall at gwmail dot gwu.edu> ---
(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...
prev parent reply other threads:[~2014-11-19 23:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-12 2:25 [Bug c/49379] New: warning from Mac OS X linker " nenad at intrepid dot com
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 ` egall at gwmail dot gwu.edu [this message]
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-uriUmA1kIm@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: link
Be 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).