public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mikulas at artax dot karlin dot mff dot cuni dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/41475] common variables cannot be expected to be aligned
Date: Sat, 26 Sep 2009 15:27:00 -0000	[thread overview]
Message-ID: <20090926152712.16445.qmail@sourceware.org> (raw)
In-Reply-To: <bug-41475-1600@http.gcc.gnu.org/bugzilla/>



------- Comment #7 from mikulas at artax dot karlin dot mff dot cuni dot cz  2009-09-26 15:27 -------
Richard Guenther: the bug caused by common symbol (in file commonalign1.o) with
the same name as data section symbol (in file commonalign2.o). In this case,
the linker redirects the common symbol to the symbol in the data section. But
the linker cannot change the content of the data section, so it cannot make
both symbols array and array2 aligned. Linker is innocent in this and giving a
warning is the best thing it can do.


-- 


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


  parent reply	other threads:[~2009-09-26 15:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-26  4:04 [Bug middle-end/41475] New: " mikulas at artax dot karlin dot mff dot cuni dot cz
2009-09-26  4:05 ` [Bug middle-end/41475] " mikulas at artax dot karlin dot mff dot cuni dot cz
2009-09-26  4:06 ` mikulas at artax dot karlin dot mff dot cuni dot cz
2009-09-26  4:14 ` mikulas at artax dot karlin dot mff dot cuni dot cz
2009-09-26 11:24 ` rguenth at gcc dot gnu dot org
2009-09-26 14:14 ` hjl dot tools at gmail dot com
2009-09-26 14:38 ` rguenth at gcc dot gnu dot org
2009-09-26 15:27 ` mikulas at artax dot karlin dot mff dot cuni dot cz [this message]
2009-09-26 19:30 ` pinskia at gcc dot gnu dot org
2009-09-27  9:51 ` mikulas at artax dot karlin dot mff dot cuni dot cz

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=20090926152712.16445.qmail@sourceware.org \
    --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).