public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/51900] [4.6/4.7 Regression] const variable initialization always zero
Date: Fri, 20 Jan 2012 07:52:00 -0000	[thread overview]
Message-ID: <bug-51900-4-LVzeeLAIdG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51900-4@http.gcc.gnu.org/bugzilla/>

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-01-20 07:33:36 UTC ---
Dunno about PE-COFF, but at least in ELF merging of .data (or .rodata) and
common symbols works by keeping the non-common symbol and it is the behavior
that GCC expects with -fcommon. If the PE-COFF linker handles it the same, then
if you can't use default_binds_local_p, you should at least copy over the
common symbol handling from it.
int i = 5;
in one file and
int i;
in another one with -fcommon just provides the int i = 5; definition and
int i; in two files provides int i = 0; definition.


  parent reply	other threads:[~2012-01-20  7:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-19 10:48 [Bug c/51900] New: [4.6 " daniel.f.starke at freenet dot de
2012-01-19 11:29 ` [Bug target/51900] " rguenth at gcc dot gnu.org
2012-01-19 12:01 ` mikpe at it dot uu.se
2012-01-19 12:18 ` daniel.f.starke at freenet dot de
2012-01-19 12:21 ` rguenth at gcc dot gnu.org
2012-01-19 15:03 ` daniel.f.starke at freenet dot de
2012-01-19 15:04 ` rguenth at gcc dot gnu.org
2012-01-19 15:16 ` [Bug target/51900] [4.6/4.7 " rguenth at gcc dot gnu.org
2012-01-20  2:50 ` ktietz at gcc dot gnu.org
2012-01-20  7:52 ` jakub at gcc dot gnu.org [this message]
2012-01-20  7:54 ` daniel.f.starke at freenet dot de
2012-01-21  0:00 ` d.g.gorbachev at gmail dot com
2012-01-23 20:38 ` ktietz at gcc dot gnu.org
2012-01-23 21:17 ` ktietz at gcc dot gnu.org

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-51900-4-LVzeeLAIdG@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).