public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/40903] LTO doesn't merge common sections properly
Date: Wed, 29 Jul 2009 18:18:00 -0000	[thread overview]
Message-ID: <20090729181838.20132.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40903-10053@http.gcc.gnu.org/bugzilla/>



------- Comment #5 from rguenther at suse dot de  2009-07-29 18:18 -------
Subject: Re:  LTO doesn't merge common sections properly

On Wed, 29 Jul 2009, rth at gcc dot gnu dot org wrote:

> ------- Comment #4 from rth at gcc dot gnu dot org  2009-07-29 18:10 -------
> So LTO still produces N output object files for N input files?
> 
> Cause you can't just output
> 
>   .comm i,4,4
>   .comm i,8,8
> 
> in one object file, and I didn't see any changes to varasm.c...

Hm, it seems to output just the first decl, so depending on the
order of files on the commandline I either get 

.comm i,4,4

or

.comm i,8,8

I have to check where that happens.

Richard.


-- 


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


  parent reply	other threads:[~2009-07-29 18:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-29 13:39 [Bug lto/40903] New: " rguenth at gcc dot gnu dot org
2009-07-29 13:39 ` [Bug lto/40903] " rguenth at gcc dot gnu dot org
2009-07-29 17:56 ` rth at gcc dot gnu dot org
2009-07-29 18:01 ` rguenther at suse dot de
2009-07-29 18:10 ` rth at gcc dot gnu dot org
2009-07-29 18:18 ` rguenther at suse dot de [this message]
2009-07-29 19:20 ` rguenth at gcc dot gnu dot org
2009-07-30 16:24 ` rguenth at gcc dot gnu dot org
2009-07-30 16:25 ` rguenth at gcc dot gnu dot org
2009-07-30 16:25 ` rguenth at gcc dot gnu dot org
2009-08-03  8:46 ` rguenth at gcc dot gnu dot 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=20090729181838.20132.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).