]>
Commit | Line | Data |
---|---|---|
adde6300 AM |
1 | /* This file is tc-avr.h |
2 | Copyright (C) 1999, 2000 Free Software Foundation, Inc. | |
3 | ||
4 | Contributed by Denis Chertykov <[email protected]> | |
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 | ||
adde6300 AM |
27 | #define TC_AVR |
28 | /* By convention, you should define this macro in the `.h' file. For | |
29 | example, `tc-m68k.h' defines `TC_M68K'. You might have to use this | |
30 | if it is necessary to add CPU specific code to the object format | |
1dab94dd | 31 | file. */ |
adde6300 AM |
32 | |
33 | #define TARGET_FORMAT "elf32-avr" | |
34 | /* This macro is the BFD target name to use when creating the output | |
1dab94dd | 35 | file. This will normally depend upon the `OBJ_FMT' macro. */ |
adde6300 AM |
36 | |
37 | #define TARGET_ARCH bfd_arch_avr | |
1dab94dd | 38 | /* This macro is the BFD architecture to pass to `bfd_set_arch_mach'. */ |
adde6300 AM |
39 | |
40 | #define TARGET_MACH 0 | |
41 | /* This macro is the BFD machine number to pass to | |
1dab94dd | 42 | `bfd_set_arch_mach'. If it is not defined, GAS will use 0. */ |
adde6300 AM |
43 | |
44 | #define TARGET_BYTES_BIG_ENDIAN 0 | |
45 | /* You should define this macro to be non-zero if the target is big | |
1dab94dd | 46 | endian, and zero if the target is little endian. */ |
adde6300 AM |
47 | |
48 | #define ONLY_STANDARD_ESCAPES | |
49 | /* If you define this macro, GAS will warn about the use of | |
1dab94dd | 50 | nonstandard escape sequences in a string. */ |
adde6300 AM |
51 | |
52 | #define md_operand(x) | |
53 | /* GAS will call this function for any expression that can not be | |
54 | recognized. When the function is called, `input_line_pointer' | |
1dab94dd | 55 | will point to the start of the expression. */ |
adde6300 AM |
56 | |
57 | void avr_parse_cons_expression (expressionS *exp, int nbytes); | |
58 | ||
59 | #define TC_PARSE_CONS_EXPRESSION(EXPR,N) avr_parse_cons_expression (EXPR,N) | |
60 | /* | |
61 | You may define this macro to parse an expression used in a data | |
62 | allocation pseudo-op such as `.word'. You can use this to | |
63 | recognize relocation directives that may appear in such directives.*/ | |
64 | ||
65 | void avr_cons_fix_new(fragS *frag,int where, int nbytes, expressionS *exp); | |
66 | ||
67 | #define TC_CONS_FIX_NEW(FRAG,WHERE,N,EXP) avr_cons_fix_new(FRAG,WHERE,N,EXP) | |
68 | /* You may define this macro to generate a fixup for a data | |
1dab94dd | 69 | allocation pseudo-op. */ |
adde6300 AM |
70 | |
71 | #define md_number_to_chars number_to_chars_littleendian | |
72 | /* This should just call either `number_to_chars_bigendian' or | |
73 | `number_to_chars_littleendian', whichever is appropriate. On | |
74 | targets like the MIPS which support options to change the | |
75 | endianness, which function to call is a runtime decision. On | |
1dab94dd | 76 | other targets, `md_number_to_chars' can be a simple macro. */ |
adde6300 AM |
77 | |
78 | #define WORKING_DOT_WORD | |
79 | /* | |
80 | `md_short_jump_size' | |
81 | `md_long_jump_size' | |
82 | `md_create_short_jump' | |
83 | `md_create_long_jump' | |
84 | If `WORKING_DOT_WORD' is defined, GAS will not do broken word | |
85 | processing (*note Broken words::.). Otherwise, you should set | |
86 | `md_short_jump_size' to the size of a short jump (a jump that is | |
87 | just long enough to jump around a long jmp) and | |
88 | `md_long_jump_size' to the size of a long jump (a jump that can go | |
89 | anywhere in the function), You should define | |
90 | `md_create_short_jump' to create a short jump around a long jump, | |
1dab94dd | 91 | and define `md_create_long_jump' to create a long jump. */ |
adde6300 AM |
92 | |
93 | #define MD_APPLY_FIX3 | |
94 | ||
95 | #define TC_HANDLES_FX_DONE | |
96 | ||
97 | #undef RELOC_EXPANSION_POSSIBLE | |
98 | /* If you define this macro, it means that `tc_gen_reloc' may return | |
99 | multiple relocation entries for a single fixup. In this case, the | |
100 | return value of `tc_gen_reloc' is a pointer to a null terminated | |
1dab94dd | 101 | array. */ |
adde6300 | 102 | |
1dab94dd | 103 | #define MD_PCREL_FROM_SECTION(FIXP, SEC) md_pcrel_from_section(FIXP, SEC) |
adde6300 AM |
104 | /* If you define this macro, it should return the offset between the |
105 | address of a PC relative fixup and the position from which the PC | |
106 | relative adjustment should be made. On many processors, the base | |
107 | of a PC relative instruction is the next instruction, so this | |
1dab94dd | 108 | macro would return the length of an instruction. */ |
adde6300 | 109 | |
00d2865b NC |
110 | extern long md_pcrel_from_section PARAMS ((struct fix *, segT)); |
111 | ||
adde6300 AM |
112 | #define LISTING_WORD_SIZE 2 |
113 | /* The number of bytes to put into a word in a listing. This affects | |
114 | the way the bytes are clumped together in the listing. For | |
115 | example, a value of 2 might print `1234 5678' where a value of 1 | |
1dab94dd | 116 | would print `12 34 56 78'. The default value is 4. */ |
adde6300 AM |
117 | |
118 | #define LEX_DOLLAR 0 | |
119 | /* AVR port uses `$' as a logical line separator */ | |
70a516ef DC |
120 | |
121 | #define TC_IMPLICIT_LCOMM_ALIGNMENT(SIZE, P2VAR) (P2VAR) = 0 | |
122 | /* An `.lcomm' directive with no explicit alignment parameter will | |
123 | use this macro to set P2VAR to the alignment that a request for | |
124 | SIZE bytes will have. The alignment is expressed as a power of | |
125 | two. If no alignment should take place, the macro definition | |
126 | should do nothing. Some targets define a `.bss' directive that is | |
127 | also affected by this macro. The default definition will set | |
128 | P2VAR to the truncated power of two of sizes up to eight bytes. */ |