SIZE(1)
π SIZE(1) π
the GNU Development Tools girlies presentβ¦ size β she lists section sizes and total size of binary files, and she ate π
β¨ NAME β¨
size β list section sizes and total size of binary files π¦
πΈ SYNOPSIS πΈ
size [-A|-B|-G|--format=compatibility]
[--help]
[-d|-o|-x|--radix=number]
[--common]
[-t|--totals]
[--target=bfdname] [-V|--version]
[-f]
[objfile...]
π DESCRIPTION π
okay so bestie, the GNU size utility lists the section sizes and the total size for every single binary file objfile on its argument list. no cap. by default you get one line of output per file β or per module, if that file is an archive. π
objfile... are the files to be examined. and if you pass none? it's giving default energy: the file a.out gets used instead. π
π OPTIONS π
the command-line options have the following meanings, and yes we're doing all of them:
-A,-B,-G,--format=compatibilityβ using one of these, you get to choose whether the output from GNUsizeresembles output from System Vsize(that's-A, or--format=sysv) or Berkeleysize(that's-B, or--format=berkeley). the default is the one-line format similar to Berkeley's. β¨ alternatively you can pick GNU format output (-G, or--format=gnu) β it's similar to Berkeley's output format, but sizes are counted differently. lowkey important.
here's an example of the Berkeley (default) format of output from size:
$ size --format=Berkeley ranlib size
text data bss dec hex filename
294880 81920 11592 388392 5ed28 ranlib
294880 81920 11888 388688 5ee50 size
so the Berkeley style output counts read only data in the "text" column, not in the "data" column. and the "dec" and "hex" columns? both display the sum of the "text", "data", and "bss" columns, in decimal and hexadecimal respectively. periodt. π
the GNU format counts read only data in the "data" column, not the "text" column, and only displays the sum of the "text", "data", and "bss" columns once, in the "total" column. the --radix option can be used to change the number base for all columns. here's the same data displayed with GNU conventions:
$ size --format=GNU ranlib size
text data bss total filename
279880 96920 11592 388392 ranlib
279880 96920 11888 388688 size
and this is the same data, but displayed closer to System V conventions:
$ size --format=SysV ranlib size
ranlib :
section size addr
.text 294880 8192
.data 81920 303104
.bss 11592 385024
Total 388392
size :
section size addr
.text 294880 8192
.data 81920 303104
.bss 11888 385024
Total 388688
iconic, honestly. π«Ά
--help,-h,-H,-?β show a summary of acceptable arguments and options. yes, four whole ways to ask for help, she's generous like that. π-d,-o,-x,--radix=numberβ using one of these you control whether the size of each section is given in decimal (-d, or--radix=10), octal (-o, or--radix=8), or hexadecimal (-x, or--radix=16). in--radix=number, only the three values (8,10,16) are supported β no freestyling. and the total size is always given in two radices: decimal and hexadecimal for-dor-xoutput, or octal and hexadecimal if you're using-o. π¦--commonβ print total size of common symbols in each file. when using Berkeley or GNU format these are included in the bss size. π-t,--totalsβ show totals of all objects listed. (Berkeley or GNU format mode only!) β--target=bfdnameβ specify that the object-code format forobjfileisbfdname. this option may not be necessary;sizecan automatically recognize many formats. she's smart like that, she doesn't need you to hold her hand. πββοΈ-v,-V,--versionβ display the version number ofsize. π-fβ ignored. this option is used by other versions of thesizeprogram, but it is not supported by the GNU Binutils version. it's giving npc. π@fileβ read command-line options fromfile. the options read are inserted in place of the original@fileoption. iffiledoes not exist, or cannot be read, then the option will be treated literally, and not removed. π
options in file are separated by whitespace. a whitespace character may be included in an option by surrounding the entire option in either single or double quotes. any character (including a backslash) may be included by prefixing the character to be included with a backslash. the file may itself contain additional @file options; any such options will be processed recursively. it's giving inception, bestie. π
π SEE ALSO π
ar(1), objdump(1), readelf(1), and the Info entries for binutils. go read them, they're the friend group. π
π COPYRIGHT π
Copyright (c) 1991-2025 Free Software Foundation, Inc. π«Ά
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License".
ngl that's the whole page, no gatekeeping, no skips, every flag accounted for π β¨
and that's a wrap bestie β this page came from binutils-2.45.50, dated 2026-01-13, and it's serving SIZE(1) energy until the end of time. slay, stay safe, and always check your bss columns. ππ¦π
π¦ where this page comes from
- ubuntu resolute: binutils-m68hc1x 1:2.45.50.20251209+3.5.3build1 Β· GPL-3.0-or-later
- ubuntu stonking: binutils-m68hc1x 1:2.45.50.20251209+3.5.3build1 Β· GPL-3.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms