[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug ld/21294] New: Binary size regression on PPC embedded (COMMONPAGESI

From: floessie.mail at gmail dot com
Subject: [Bug ld/21294] New: Binary size regression on PPC embedded (COMMONPAGESIZE 64k)
Date: Thu, 23 Mar 2017 08:14:36 +0000


            Bug ID: 21294
           Summary: Binary size regression on PPC embedded (COMMONPAGESIZE
           Product: binutils
           Version: 2.27
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: ld
          Assignee: unassigned at sourceware dot org
          Reporter: floessie.mail at gmail dot com
  Target Milestone: ---


Since updating our toolchains for PPC 405, e300c3, and e500v2 we experience a
massive size increase for small binaries. Our 405 target has very small
storage, and as the rootfs contains a lot of small binaries, we can't supply
images linked with binutils 2.27 or 2.28 anymore.

I filed a bug over at crosstool-ng [1] to get some help, and Alexey Neyman was
kind enough to give me a hint to COMMONPAGESIZE. Doing some research, I found
out that it was raised from 4k to 64k in 2014 [2]. You discussed about the
impact on embedded, but it wasn't considered as an obstacle. Maybe that should
be reconsidered.

Is it possible to treat embedded, size constrained targets differently than
servers? There's a special 4k COMMONPAGESIZE for __QNXTARGET__. Or would it be
possible to add a configure option for this? Or is there already another
mechanism to alter COMMONPAGESIZE?

Kind regards,

[1] https://github.com/crosstool-ng/crosstool-ng/issues/656
[2] https://sourceware.org/ml/binutils/2014-12/msg00165.html

You are receiving this mail because:
You are on the CC list for the bug.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]