| 1 | /* This file is tc-avr.h
|
|---|
| 2 | Copyright 1999, 2000, 2001, 2002 Free Software Foundation, Inc.
|
|---|
| 3 |
|
|---|
| 4 | Contributed by Denis Chertykov <denisc@overta.ru>
|
|---|
| 5 |
|
|---|
| 6 | This file is part of GAS, the GNU Assembler.
|
|---|
| 7 |
|
|---|
| 8 | GAS is free software; you can redistribute it and/or modify
|
|---|
| 9 | it under the terms of the GNU General Public License as published by
|
|---|
| 10 | the Free Software Foundation; either version 2, or (at your option)
|
|---|
| 11 | any later version.
|
|---|
| 12 |
|
|---|
| 13 | GAS is distributed in the hope that it will be useful,
|
|---|
| 14 | but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|---|
| 15 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|---|
| 16 | GNU General Public License for more details.
|
|---|
| 17 |
|
|---|
| 18 | You should have received a copy of the GNU General Public License
|
|---|
| 19 | along with GAS; see the file COPYING. If not, write to the Free
|
|---|
| 20 | Software Foundation, 59 Temple Place - Suite 330, Boston, MA
|
|---|
| 21 | 02111-1307, USA. */
|
|---|
| 22 |
|
|---|
| 23 | #ifndef BFD_ASSEMBLER
|
|---|
| 24 | #error AVR support requires BFD_ASSEMBLER
|
|---|
| 25 | #endif
|
|---|
| 26 |
|
|---|
| 27 | /* By convention, you should define this macro in the `.h' file. For
|
|---|
| 28 | example, `tc-m68k.h' defines `TC_M68K'. You might have to use this
|
|---|
| 29 | if it is necessary to add CPU specific code to the object format
|
|---|
| 30 | file. */
|
|---|
| 31 | #define TC_AVR
|
|---|
| 32 |
|
|---|
| 33 | /* This macro is the BFD target name to use when creating the output
|
|---|
| 34 | file. This will normally depend upon the `OBJ_FMT' macro. */
|
|---|
| 35 | #define TARGET_FORMAT "elf32-avr"
|
|---|
| 36 |
|
|---|
| 37 | /* This macro is the BFD architecture to pass to `bfd_set_arch_mach'. */
|
|---|
| 38 | #define TARGET_ARCH bfd_arch_avr
|
|---|
| 39 |
|
|---|
| 40 | /* This macro is the BFD machine number to pass to
|
|---|
| 41 | `bfd_set_arch_mach'. If it is not defined, GAS will use 0. */
|
|---|
| 42 | #define TARGET_MACH 0
|
|---|
| 43 |
|
|---|
| 44 | /* You should define this macro to be non-zero if the target is big
|
|---|
| 45 | endian, and zero if the target is little endian. */
|
|---|
| 46 | #define TARGET_BYTES_BIG_ENDIAN 0
|
|---|
| 47 |
|
|---|
| 48 | /* If you define this macro, GAS will warn about the use of
|
|---|
| 49 | nonstandard escape sequences in a string. */
|
|---|
| 50 | #define ONLY_STANDARD_ESCAPES
|
|---|
| 51 |
|
|---|
| 52 | /* GAS will call this function for any expression that can not be
|
|---|
| 53 | recognized. When the function is called, `input_line_pointer'
|
|---|
| 54 | will point to the start of the expression. */
|
|---|
| 55 | #define md_operand(x)
|
|---|
| 56 |
|
|---|
| 57 | /* You may define this macro to parse an expression used in a data
|
|---|
| 58 | allocation pseudo-op such as `.word'. You can use this to
|
|---|
| 59 | recognize relocation directives that may appear in such directives. */
|
|---|
| 60 | #define TC_PARSE_CONS_EXPRESSION(EXPR,N) avr_parse_cons_expression (EXPR,N)
|
|---|
| 61 | void avr_parse_cons_expression (expressionS *exp, int nbytes);
|
|---|
| 62 |
|
|---|
| 63 | /* You may define this macro to generate a fixup for a data
|
|---|
| 64 | allocation pseudo-op. */
|
|---|
| 65 | #define TC_CONS_FIX_NEW(FRAG,WHERE,N,EXP) avr_cons_fix_new(FRAG,WHERE,N,EXP)
|
|---|
| 66 | void avr_cons_fix_new(fragS *frag,int where, int nbytes, expressionS *exp);
|
|---|
| 67 |
|
|---|
| 68 | /* This should just call either `number_to_chars_bigendian' or
|
|---|
| 69 | `number_to_chars_littleendian', whichever is appropriate. On
|
|---|
| 70 | targets like the MIPS which support options to change the
|
|---|
| 71 | endianness, which function to call is a runtime decision. On
|
|---|
| 72 | other targets, `md_number_to_chars' can be a simple macro. */
|
|---|
| 73 | #define md_number_to_chars number_to_chars_littleendian
|
|---|
| 74 |
|
|---|
| 75 | /* `md_short_jump_size'
|
|---|
| 76 | `md_long_jump_size'
|
|---|
| 77 | `md_create_short_jump'
|
|---|
| 78 | `md_create_long_jump'
|
|---|
| 79 | If `WORKING_DOT_WORD' is defined, GAS will not do broken word
|
|---|
| 80 | processing (*note Broken words::.). Otherwise, you should set
|
|---|
| 81 | `md_short_jump_size' to the size of a short jump (a jump that is
|
|---|
| 82 | just long enough to jump around a long jmp) and
|
|---|
| 83 | `md_long_jump_size' to the size of a long jump (a jump that can go
|
|---|
| 84 | anywhere in the function), You should define
|
|---|
| 85 | `md_create_short_jump' to create a short jump around a long jump,
|
|---|
| 86 | and define `md_create_long_jump' to create a long jump. */
|
|---|
| 87 | #define WORKING_DOT_WORD
|
|---|
| 88 |
|
|---|
| 89 | /* If you define this macro, it means that `tc_gen_reloc' may return
|
|---|
| 90 | multiple relocation entries for a single fixup. In this case, the
|
|---|
| 91 | return value of `tc_gen_reloc' is a pointer to a null terminated
|
|---|
| 92 | array. */
|
|---|
| 93 | #undef RELOC_EXPANSION_POSSIBLE
|
|---|
| 94 |
|
|---|
| 95 | /* No shared lib support, so we don't need to ensure externally
|
|---|
| 96 | visible symbols can be overridden. */
|
|---|
| 97 | #define EXTERN_FORCE_RELOC 0
|
|---|
| 98 |
|
|---|
| 99 | /* Values passed to md_apply_fix3 don't include the symbol value. */
|
|---|
| 100 | #define MD_APPLY_SYM_VALUE(FIX) 0
|
|---|
| 101 |
|
|---|
| 102 | /* If you define this macro, it should return the offset between the
|
|---|
| 103 | address of a PC relative fixup and the position from which the PC
|
|---|
| 104 | relative adjustment should be made. On many processors, the base
|
|---|
| 105 | of a PC relative instruction is the next instruction, so this
|
|---|
| 106 | macro would return the length of an instruction. */
|
|---|
| 107 | #define MD_PCREL_FROM_SECTION(FIX, SEC) md_pcrel_from_section(FIX, SEC)
|
|---|
| 108 | extern long md_pcrel_from_section PARAMS ((struct fix *, segT));
|
|---|
| 109 |
|
|---|
| 110 | /* The number of bytes to put into a word in a listing. This affects
|
|---|
| 111 | the way the bytes are clumped together in the listing. For
|
|---|
| 112 | example, a value of 2 might print `1234 5678' where a value of 1
|
|---|
| 113 | would print `12 34 56 78'. The default value is 4. */
|
|---|
| 114 | #define LISTING_WORD_SIZE 2
|
|---|
| 115 |
|
|---|
| 116 | /* AVR port uses `$' as a logical line separator */
|
|---|
| 117 | #define LEX_DOLLAR 0
|
|---|
| 118 |
|
|---|
| 119 | /* An `.lcomm' directive with no explicit alignment parameter will
|
|---|
| 120 | use this macro to set P2VAR to the alignment that a request for
|
|---|
| 121 | SIZE bytes will have. The alignment is expressed as a power of
|
|---|
| 122 | two. If no alignment should take place, the macro definition
|
|---|
| 123 | should do nothing. Some targets define a `.bss' directive that is
|
|---|
| 124 | also affected by this macro. The default definition will set
|
|---|
| 125 | P2VAR to the truncated power of two of sizes up to eight bytes. */
|
|---|
| 126 | #define TC_IMPLICIT_LCOMM_ALIGNMENT(SIZE, P2VAR) (P2VAR) = 0
|
|---|