Searched refs:EIND (Results 1 – 7 of 7) sorted by relevance
65 #define EIND 0x5C macro870 avr_cpu->pc = ((sram[EIND] << 16) | read_word (REGZ)) & PC_MASK; in step_once()886 do_call (cpu, (sram[EIND] << 16) | read_word (REGZ)); in step_once()
21654 section on @code{EIND} and linker stubs below.21743 @subsubsection @code{EIND} and Devices with More Than 128 Ki Bytes of Flash21744 @cindex @code{EIND}21752 @code{EIND} that serves as most significant part of the target address21761 The compiler never sets @code{EIND}.21764 The compiler uses @code{EIND} implicitly in @code{EICALL}/@code{EIJMP}21765 instructions or might read @code{EIND} directly in order to emulate an21769 The compiler assumes that @code{EIND} never changes during the startup21770 code or during the application. In particular, @code{EIND} is not21788 The default linker script is arranged for code with @code{EIND = 0}.[all …]
20387 section on 'EIND' and linker stubs below.20461 3.19.6.1 'EIND' and Devices with More Than 128 Ki Bytes of Flash20470 called 'EIND' that serves as most significant part of the target address20476 * The compiler never sets 'EIND'.20478 * The compiler uses 'EIND' implicitly in 'EICALL'/'EIJMP'20479 instructions or might read 'EIND' directly in order to emulate an20482 * The compiler assumes that 'EIND' never changes during the startup20483 code or during the application. In particular, 'EIND' is not20498 * The default linker script is arranged for code with 'EIND = 0'. If20499 code is supposed to work for a setup with 'EIND != 0', a custom[all …]
7069 * doc/invoke.texi (AVR Options): New subsubsection to explain EIND7464 (__tablejump__): Consistently use EIND for indirect jump/call.9126 * config/avr/libgcc.S (__tablejump__): Use RET instead of EIND +
31668 Some more notes on EIND usage and reorder EIND subsection.
44616 (EIND and Devices with more than 128 Ki Bytes of Flash): Likewise.
10345 + Handling of EIND and indirect jumps on devices with more than