|AVR Libc Home Page||AVR Libc Development Pages|
|Main Page||User Manual||Library Reference||FAQ||Alphabetical Index||Example Projects|
texinfofiles. Command-line options are explained in detail in the manual page.
Compile code for architecture. Currently known architectures are
|Simple CPU core, only assembler support|
|"Classic" CPU core, up to 8 KB of ROM|
|"Classic" CPU core with 'MOVW' and 'LPM Rx, Z[+]' instruction, up to 8 KB of ROM|
|"Classic" CPU core, 16 KB to 64 KB of ROM|
|"Classic" CPU core, 128 KB of ROM|
|"Classic" CPU core with 'MOVW' and 'LPM Rx, Z[+]' instruction, 16 KB to 64 KB of ROM|
|"Enhanced" CPU core, up to 8 KB of ROM|
|"Enhanced" CPU core, 16 KB to 64 KB of ROM|
|"Enhanced" CPU core, 128 KB of ROM|
|"Enhanced" CPU core, 256 KB of ROM|
 New in GCC 4.2
 Unofficial patch for GCC 4.1
 New in GCC 4.2.3
 New in GCC 4.3
By default, code is generated for the avr2 architecture.
Note that when only using
-mmcu=architecture but no
-mmcu=MCU type, including the file
<avr/io.h> cannot work since it cannot decide which device's definitions to select.
The following MCU types are currently understood by avr-gcc. The table matches them against the corresponding avr-gcc architecture name, and shows the preprocessor symbol declared by the
 'avr25' architecture is new in GCC 4.2
 'avr35' architecture is new in GCC 4.2.3
Change the order of register assignment. The default is
r24, r25, r18, r19, r20, r21, r22, r23, r30, r31, r26, r27, r28, r29, r17, r16, r15, r14, r13, r12, r11, r10, r9, r8, r7, r6, r5, r4, r3, r2, r0, r1
Order 1 uses
r18, r19, r20, r21, r22, r23, r24, r25, r30, r31, r26, r27, r28, r29, r17, r16, r15, r14, r13, r12, r11, r10, r9, r8, r7, r6, r5, r4, r3, r2, r0, r1
Order 2 uses
r25, r24, r23, r22, r21, r20, r19, r18, r30, r31, r26, r27, r28, r29, r17, r16, r15, r14, r13, r12, r11, r10, r9, r8, r7, r6, r5, r4, r3, r2, r1, r0
int to be an 8-bit integer. Note that this is not really supported by
avr-libc, so it should normally not be used. The default is to use 16-bit integers.
Generates code that changes the stack pointer without disabling interrupts. Normally, the state of the status register
SREG is saved in a temporary register, interrupts are disabled while changing the stack pointer, and
SREG is restored.
Specifying this option will define the preprocessor macro
__NO_INTERRUPTS__ to the value 1.
Use subroutines for function prologue/epilogue. For complex functions that use many registers (that needs to be saved/restored on function entry/exit), this saves some space at the cost of a slightly increased execution time.
Change only the low 8 bits of the stack pointer.
Do not generate tablejump instructions. By default, jump tables can be used to optimize
switch statements. When turned off, sequences of compare statements are used instead. Jump tables are usually faster to execute on average, but in particular for
switch statements where most of the jumps would go to the default label, they might waste a bit of flash memory.
rjmp/rcall (limited range) on >8K devices. On
avr4 architectures (less than 8 KB or flash memory), this is always the case. On
avr5 architectures, calls and jumps to targets outside the current function will by default use
jmp/call instructions that can cover the entire address range, but that require more flash ROM and execution time.
Dump the internal compilation result called "RTL" into comments in the generated assembler code. Used for debugging avr-gcc.
Dump the address, size, and relative cost of each statement into comments in the generated assembler code. Used for debugging avr-gcc.
Generate lots of debugging information to
Optimization level n. Increasing n is meant to optimize more, an optimization level of 0 means no optimization at all, which is the default if no
-O option is present. The special option
-Os is meant to turn on all
-O2 optimizations that are not expected to increase code size.
Note that at
-O3, gcc attempts to inline all "simple" functions. For the AVR target, this will normally constitute a large pessimization due to the code increasement. The only other optimization turned on with
-frename-registers, which could rather be enabled manually instead.
-O option is equivalent to
Note also that turning off all optimizations will prevent some warnings from being issued since the generation of those warnings depends on code analysis steps that are only performed when optimizing (unreachable code, unused variables).
See also the appropriate FAQ entry for issues regarding debugging optimized code.
Generate debugging information that can be used by avr-gdb.
Assume a "freestanding" environment as per the C standard. This turns off automatic builtin functions (though they can still be reached by prepending
__builtin_ to the actual function name). It also makes the compiler not complain when
main() is declared with a
void return type which makes some sense in a microcontroller environment where the application cannot meaningfully provide a return value to its environment (in most cases,
main() won't even return anyway). However, this also turns off all optimizations normally done by the compiler which assume that functions known by a certain name behave as described by the standard. E. g., applying the function strlen() to a literal string will normally cause the compiler to immediately replace that call by the actual length of the string, while with
-ffreestanding, it will always call strlen() at run-time.
Make any unqualfied
char type an unsigned char. Without this option, they default to a signed char.
Make any unqualified bitfield type unsigned. By default, they are signed.
Allocate to an
enum type only as many bytes as it needs for the declared range of possible values. Specifically, the enum type will be equivalent to the smallest integer type which has enough room.
Pack all structure members together without holes.
avr-as understands the same
-mmcu= options as avr-gcc. By default, avr2 is assumed, but this can be altered by using the appropriate
.arch pseudo-instruction inside the assembler source file.
Turns off opcode checking for the actual MCU type, and allows any possible AVR opcode to be assembled.
Don't emit a warning when trying to skip a 2-word instruction with a
CPSE/SBIC/SBIS/SBRC/SBRS instruction. Early AVR devices suffered from a hardware bug where these instructions could not be properly skipped.
RJMP/RCALL instructions, don't allow the target address to wrap around for devices that have more than 8 KB of memory.
.stabs debugging symbols for assembler source lines. This enables avr-gdb to trace through assembler source files. This option must not be used when assembling sources that have been generated by the C compiler; these files already contain the appropriate line number information from the C source files.
Turn on the assembler listing. The sub-options are:
comit false conditionals
domit debugging directives
hinclude high-level source
minclude macro expansions
nomit forms processing
=file set the name of the listing file
The various sub-options can be combined into a single
-a option list; =file must be the last one in that case.
-Wa(see above), so in order to include the C source code into the assembler listing in file
foo.lst, when compiling
foo.c, the following compiler command-line can be used:
$ avr-gcc -c -O foo.c -o foo.o -Wa,-ahls=foo.lst
In order to pass an assembler file through the C preprocessor first, and have the assembler generate line number debugging information for it, the following command can be used:
$ avr-gcc -c -x assembler-with-cpp -o foo.o foo.S -Wa,--gstabs
Note that on Unix systems that have case-distinguishing file systems, specifying a file name with the suffix
.S (upper-case letter S) will make the compiler automatically assume
-x assembler-with-cpp, while using
.s would pass the file directly to the assembler (no preprocessing done).
Locate the archive library named
.a, and use it to resolve currently unresolved symbols from it. The library is searched along a path that consists of builtin pathname entries that have been specified at compile time (e. g.
/usr/local/avr/lib on Unix systems), possibly extended by pathname entries as specified by
-L options (that must precede the
-l options on the command-line).
Additional location to look for archive libraries requested by
Define a global symbol symbol using expr as the value.
Print a linker map to
Print a linker map to mapfile.
Output a cross reference table to the map file (in case
-Map is also present), or to
Start section sectionname at absolute address org.
text section at org, respectively.
Use scriptfile as the linker script, replacing the default linker script. Default linker scripts are stored in a system-specific location (e. g. under
/usr/local/avr/lib/ldscripts on Unix systems), and consist of the AVR architecture name (avr2 through avr5) with the suffix
.x appended. They describe how the various memory sections will be linked together.
.o (object files) and
.a (object libraries) are provided to the linker.
System libraries are usually not passed by their explicit filename but rather using the
-l option which uses an abbreviated form of the archive filename (see above). avr-libc ships two system libraries,
libm.a. While the standard library
libc.a will always be searched for unresolved references when the linker is started using the C compiler frontend (i. e., there's always at least one implied
-lc option), the mathematics library
libm.a needs to be explicitly requested using
-lm. See also the entry in the FAQ explaining this.
Conventionally, Makefiles use the
LDLIBS to keep track of
-l (and possibly
-L) options that should only be appended to the C compiler command-line when linking the final binary. In contrast, the macro
LDFLAGS is used to store other command-line options to the C compiler that should be passed as options during the linking stage. The difference is that options are placed early on the command-line, while libraries are put at the end since they are to be used to resolve global symbols that are still unresolved at this point.
Specific linker flags can be passed from the C compiler command-line using the
-Wl compiler option, see above. This option requires that there be no spaces in the appended linker option, while some of the linker options above (like
--defsym) would require a space. In these situations, the space can be replaced by an equal sign as well. For example, the following command-line can be used to compile
foo.c into an executable, and also produce a link map that contains a cross-reference list in the file
$ avr-gcc -O -o foo.out -Wl,-Map=foo.map -Wl,--cref foo.c
Alternatively, a comma as a placeholder will be replaced by a space before passing the option to the linker. So for a device with external SRAM, the following command-line would cause the linker to place the data segment at address 0x2000 in the SRAM:
$ avr-gcc -mmcu=atmega128 -o foo.out -Wl,-Tdata,0x802000
See the explanation of the data section for why 0x800000 needs to be added to the actual value. Note that the stack will still remain in internal RAM, through the symbol
__stack that is provided by the run-time startup code. This is probably a good idea anyway (since internal RAM access is faster), and even required for some early devices that had hardware bugs preventing them from using a stack in external RAM. Note also that the heap for
malloc() will still be placed after all the variables in the data section, so in this situation, no stack/heap collision can occur.
In order to relocate the stack from its default location at the top of interns RAM, the value of the symbol
__stack can be changed on the linker command-line. As the linker is typically called from the compiler frontend, this can be achieved using a compiler option like
The above will make the code use stack space from RAM address 0x3ff downwards. The amount of stack space available then depends on the bottom address of internal RAM for a particular device. It is the responsibility of the application to ensure the stack does not grow out of bounds, as well as to arrange for the stack to not collide with variable allocations made by the compiler (sections .data and .bss).