public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "john.frankish at outlook dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcc/98395] New: libgcc_s.so.1 almost 10x bigger in gcc-10.2 than gcc-9.2
Date: Sat, 19 Dec 2020 19:57:31 +0000	[thread overview]
Message-ID: <bug-98395-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98395

            Bug ID: 98395
           Summary: libgcc_s.so.1 almost 10x bigger in gcc-10.2 than
                    gcc-9.2
           Product: gcc
           Version: 10.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libgcc
          Assignee: unassigned at gcc dot gnu.org
          Reporter: john.frankish at outlook dot com
  Target Milestone: ---

The libgcc_s.so.1 library built with gcc-10.2 is 580kb, whereas the same
library built with gcc-9.2 is 75kb.

Both were built on an x86_64 system with:

CC="gcc -mtune=generic -Os -pipe" CXX="g++ -mtune=generic -Os -pipe"
../configure --prefix=/usr/local --enable-languages=c,c++ --disable-multilib
--disable-bootstrap --with-system-zlib --libexecdir=/usr/local/lib

The almost ten-fold increase in size would seem to indicate something is wrong,
but what?

             reply	other threads:[~2020-12-19 19:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-19 19:57 john.frankish at outlook dot com [this message]
2020-12-19 20:37 ` [Bug libgcc/98395] " schwab@linux-m68k.org
2020-12-19 20:39 ` john.frankish at outlook dot com
2020-12-19 21:16 ` jakub at gcc dot gnu.org
2020-12-19 21:55 ` john.frankish at outlook dot com
2020-12-21  8:34 ` marxin at gcc dot gnu.org
2020-12-23 12:54 ` john.frankish at outlook dot com

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