Bug ID 1152590
Summary cross-avr-gcc* are huge
Classification openSUSE
Product openSUSE Tumbleweed
Version Current
Hardware Other
OS Other
Status NEW
Severity Normal
Priority P5 - None
Component Development
Assignee rguenther@suse.com
Reporter jslaby@suse.com
QA Contact qa-bugs@suse.de
Found By ---
Blocker ---

I want to cross-compile for avrs, so I installed cross-avr-gcc9, but the rpm is
HUGE. Look:
https://download.opensuse.org/repositories/devel:/gcc/openSUSE_Factory/x86_64/?C=S;O=D

cross-avr and cross-rx binaries seem to be unstripped -- no debuginfo package,
the debuginfo is inline.

Picking some of the files from the rpm:
187818848 Sep 23 16:21 /usr/lib64/gcc/avr/9/cc1
199320384 Sep 23 16:21 /usr/lib64/gcc/avr/9/cc1plus
179107056 Sep 23 16:21 /usr/lib64/gcc/avr/9/lto1

Almost 200M each...

# objdump -h /usr/lib64/gcc/avr/9/lto1 |grep \\.debug
 31 .debug_aranges 0000db70  0000000000000000  0000000000000000  00d21db0  2**4
 32 .debug_info   04ad324b  0000000000000000  0000000000000000  00d2f920  2**0
 33 .debug_abbrev 001aa282  0000000000000000  0000000000000000  05802b6b  2**0
 34 .debug_line   00c54dd7  0000000000000000  0000000000000000  059acded  2**0
 35 .debug_str    0053d6db  0000000000000000  0000000000000000  06601bc4  2**0
 36 .debug_loc    02f2cce9  0000000000000000  0000000000000000  06b3f29f  2**0
 37 .debug_ranges 00e77270  0000000000000000  0000000000000000  09a6bf90  2**4

On the other hand, from cross-arm-gcc9:
18859160 Aug 23 14:00 /usr/lib64/gcc/arm-suse-linux-gnueabi/9/cc1
20189880 Aug 23 14:00 /usr/lib64/gcc/arm-suse-linux-gnueabi/9/cc1plus
17903416 Aug 23 14:00 /usr/lib64/gcc/arm-suse-linux-gnueabi/9/lto1

By the order of magnitude smaller: around 20M.

# objdump -h /usr/lib64/gcc/arm-suse-linux-gnueabi/9/lto1 |grep \\.debug
<Nothing>


So stripping lto1 manually:
# cp /usr/lib64/gcc/avr/9/lto1 .
# strip /usr/lib64/gcc/avr/9/lto1
# ll -h lto1 /usr/lib64/gcc/avr/9/lto1
-rwxr-xr-x 1 root root 171M  1.������j 09.07 lto1
-rwxr-xr-x 1 root root  14M  1.������j 09.07 /usr/lib64/gcc/avr/9/lto1

So what went wrong during the build?


You are receiving this mail because: