public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Poison BL." <poisonbl@gmail.com>
To: gentoo-user <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] bloated by gcc
Date: Mon, 29 Sep 2014 12:20:32 -0400	[thread overview]
Message-ID: <CAOTuDKqbEpTO+9gjo4hSPKQ1AcANowf0qPG94dOnE=tM2y+HFw@mail.gmail.com> (raw)
In-Reply-To: <CAKpSnpLZUMCxSKCvr=5NUeN3v_-aDk0CO5OEGXB8JMiePfH+nQ@mail.gmail.com>

On Mon, Sep 29, 2014 at 12:02 PM, Jorge Almeida <jjalmeida@gmail.com> wrote:
> On Mon, Sep 29, 2014 at 4:25 PM, Kerin Millar <kerframil@fastmail.co.uk> wrote:
>> On 29/09/2014 16:10, Jorge Almeida wrote:
>>>
>
>>>>> I'm having a somewhat disgusting issue on my Gentoo: binaries are
>>>>> unaccountably large.
>>>>
>
>>
>> You might consider making contact with the toolchain herd at gentoo or
>> filing a bug. I, for one, would be interested to know the outcome.
>>
> Well, I suppose this one is the list every gentooer subscribes to, and
> I would like to be sure I'm not making something silly before filing a
> bug...
>
> Meanwhile, I tried compiling with clang. It produces similar sizes in
> Gentoo and in LFS (same i3 computer), although about 200B larger than
> in Slackware/atom. So, it really seems to be a gcc issue.
>
> thanks
>
> Jorge
>

Just the off the top of my head thoughts on how I'd approach this. GCC
has the option to not clean up its temp files used during the build,
as well as outputting annotated assembly mid-build. The latter might
be the most enlightening on what's being treated differently in the
output of the various systems. I don't use those tricks often enough
to remember what flags are what off the top of my head, since I only
really dig that deep when playing with my avr based toys, but just a
couple ideas I thought I'd pass along.

-- 
Poison [BLX]
Joshua M. Murphy


  reply	other threads:[~2014-09-29 16:20 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-28  8:44 [gentoo-user] bloated by gcc Jorge Almeida
2014-09-28 21:56 ` [gentoo-user] " walt
2014-09-28 23:37   ` Jorge Almeida
2014-09-30  7:04     ` J. Roeleveld
2014-09-30  7:35       ` Jorge Almeida
2014-09-29 11:18 ` [gentoo-user] " Walter Dnes
2014-09-29 11:45   ` Jorge Almeida
2014-09-29 15:15     ` Walter Dnes
2014-09-29 15:32       ` Jorge Almeida
2014-09-29 17:51         ` Walter Dnes
2014-09-29 14:50 ` Marc Stürmer
2014-09-29 15:10   ` Jorge Almeida
2014-09-29 15:25     ` Kerin Millar
2014-09-29 16:02       ` Jorge Almeida
2014-09-29 16:20         ` Poison BL. [this message]
2014-09-29 17:33           ` Jorge Almeida
2014-09-29 17:16   ` Rich Freeman
2014-09-29 16:35 ` Daniel Troeder
2014-09-29 17:28   ` Jorge Almeida
2014-09-29 18:03   ` Stroller
2014-09-29 18:26     ` Jorge Almeida
2014-09-29 19:13       ` Jorge Almeida

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='CAOTuDKqbEpTO+9gjo4hSPKQ1AcANowf0qPG94dOnE=tM2y+HFw@mail.gmail.com' \
    --to=poisonbl@gmail.com \
    --cc=gentoo-user@lists.gentoo.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