SIZE(1)
π SIZE(1) π
okay bestie, so this is the size page from GNU Development Tools, and it's genuinely one of the most useful little gremlins in the binutils fam. it just... tells you how big stuff is. iconic behavior honestly β¨
πΈ 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 β¨
so the GNU size utility lists the section sizes and the total size for each of the binary files objfile on its argument list. that's the whole vibe. π
by default you get one line of output per file β or per module, if the file happens to be an archive. slay.
objfile... are the files to be examined. and if you specify literally none of them? it just falls back to the file "a.out" instead. no cap, that's the default. π¦
π OPTIONS π
the command-line options have the following meanings, and yes we're going through every single one because you deserve to know:
-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 the GNU format output (that's-G, or--format=gnu) β it's similar to Berkeley's output format, but sizes are counted differently. yes, differently. keep reading. π₯
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. told you. π
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
three formats, three whole aesthetics. π
--help,-h,-H,-?β show a summary of acceptable arguments and options. four whole ways to ask for help, they really said redundancy is self-care. π-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). and in--radix=number, only the three values (8,10,16) are supported β don't get creative, bestie. also: 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. iykyk. π§-t,--totalsβ show totals of all objects listed (Berkeley or GNU format mode only). so if you're in SysV mode, this one's just gonna sit there. π--target=bfdnameβ specify that the object-code format for objfile is bfdname. this option may not be necessary;sizecan automatically recognize many formats. it's giving "optional but supportive." π-v,-V,--versionβ display the version number ofsize. simple, clean, iconic. β-fβ ignored. literally ignored. this option is used by other versions of thesizeprogram, but it is not supported by the GNU Binutils version. so it's there, it parses, and it does absolutely nothing. π@fileβ read command-line options from file. the options read are inserted in place of the original@fileoption. if file does 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 turtles all the way down, fr fr. π’
π¦ SEE ALSO π¦
ar(1), objdump(1), readelf(1), and the Info entries for binutils. go read them, they're all main character energy in their own way. π
π COPYRIGHT π
Copyright (c) 1991-2026 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". π
and that's the whole page, bestie! this one's from binutils-2.47, dated 2026-09-30, and it lives at SIZE(1) in the manual. mwah. ππΈ
π¦ where this page comes from
- arch rolling: riscv64-elf-binutils 2.47-1 Β· GPL
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms