public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mrs at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/52571] vectorizer changes alignment of common symbols
Date: Thu, 10 May 2012 16:11:00 -0000	[thread overview]
Message-ID: <bug-52571-4-2rtAOma2aw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52571-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #14 from mrs at gcc dot gnu.org <mrs at gcc dot gnu.org> 2012-05-10 16:06:20 UTC ---
I'd disagree with that.  I suspect 99% of them are not overridden, just like
99% of C functions are not weak and not overridden either.  As for what should
be done, doesn't matter, as since the system places no constraint on selection
for the linker, there simply is nothing one can depend upon.  I agree,
selecting the one with the maximal alignment would be nice, but, just be wary
this may cause one to try and make use of that property, and this just would
turn into a complex form of bug pushing or bug hiding.

Uncommoning things I think might well be slightly harder than trivial.  A ctor
is allowed to dynamically load a shared library, that defines a symbol, maybe,
conditional on the environment.  But with proper escape analysis, seems like
one can figure it all out, just be careful with the edge cases.


      parent reply	other threads:[~2012-05-10 16:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-12 21:53 [Bug tree-optimization/52571] New: " ian at airs dot com
2012-03-12 22:10 ` [Bug tree-optimization/52571] " pinskia at gcc dot gnu.org
2012-03-13  8:35 ` rguenth at gcc dot gnu.org
2012-03-13 17:12 ` ian at airs dot com
2012-03-14  9:39 ` rguenther at suse dot de
2012-03-14 13:02 ` rguenth at gcc dot gnu.org
2012-03-14 13:02 ` rguenth at gcc dot gnu.org
2012-03-16 16:49 ` rguenth at gcc dot gnu.org
2012-03-20 15:33 ` ro at gcc dot gnu.org
2012-03-20 15:57 ` dominiq at lps dot ens.fr
2012-03-20 16:03 ` dominiq at lps dot ens.fr
2012-04-09 23:54 ` mrs at gcc dot gnu.org
2012-05-10 11:45 ` rguenth at gcc dot gnu.org
2012-05-10 12:15 ` jakub at gcc dot gnu.org
2012-05-10 16:11 ` mrs at gcc dot gnu.org [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-52571-4-2rtAOma2aw@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).