From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Felipe Gohring <lipee36@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: GCC update increased the file size by 4x on PowerPC port
Date: Mon, 07 Jan 2019 16:59:00 -0000 [thread overview]
Message-ID: <CAH6eHdS_=QWDwN-4gUZP+L6=4=ijSCc6Mg9tAbPShJ=Rh4orTg@mail.gmail.com> (raw)
In-Reply-To: <b7fa533fe1b9abff32933d834d34ddeba6189969.camel@mengyan1223.wang>
On Mon, 7 Jan 2019 at 16:56, Xi Ruoyao wrote:
>
> On 2019-01-07 11:14 -0500, Felipe Gohring wrote:
> > Hello,
> > recently, I have updated my GCC PowerPC port from 6.3 to 8.2
> > As my architecture relies on SPE extension, I am using the SPE brench of
> > GCC (powerpc-eabispe-*).
> >
> > Now, my question is related to the generated code. When using V6.3, I had
> > files of about 10k. After upgrading to V8.2, the very same file has more
> > than 40k. Why is that? Please keep in mind that I am using exactly the same
> > compilation flags (*-m32 -mmfpgpr -mabi=spe -mfloat-gprs=double -nostdlib
> > -ffreestanding -fno-builtin -O0 -g3 -std=c11 -Wno-packed-bitfield-compat
> > -Wall -Werror*) and source code, the only thing changing is the compiler
> > version. I wouldn't mind having a memory footprint a bit bigger, but the
> > overhead added is beyond acceptable.
>
> Is there any difference w/o -g3? A increased size of debugging symbols
> is not a bug and may provide better debug information for GDB. If the
> object code itself bloats there may be a regression.
And there's no memory overhead for debug info.
Compare the sizes of the files by using the 'size' command, not 'ls -l'.
next prev parent reply other threads:[~2019-01-07 16:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-07 16:12 Felipe Gohring
2019-01-07 16:56 ` Xi Ruoyao
2019-01-07 16:59 ` Jonathan Wakely [this message]
2019-01-07 17:23 ` Segher Boessenkool
2019-01-07 18:57 ` Felipe Gohring
2019-01-07 21:16 ` Felipe Gohring
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='CAH6eHdS_=QWDwN-4gUZP+L6=4=ijSCc6Mg9tAbPShJ=Rh4orTg@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=lipee36@gmail.com \
/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).