+ /* How many bytes are involved? */
+ unsigned fx_size : 8;
+
+ bfd_reloc_code_real_type fx_r_type;
+
+ /* Which frag does this fix apply to? */
+ fragS *fx_frag;
+
+ /* The location within the frag where the fixup occurs. */
+ unsigned long fx_where;
+
+ /* NULL or Symbol whose value we add in. */
+ symbolS *fx_addsy;
+
+ /* NULL or Symbol whose value we subtract. */
+ symbolS *fx_subsy;
+
+ /* Absolute number we add in. */
+ valueT fx_offset;
+
+ /* The value of dot when the fixup expression was parsed. */
+ addressT fx_dot_value;
+
+ /* The frag fx_dot_value is based on. */
+ fragS *fx_dot_frag;
+
+ /* This field is sort of misnamed. It appears to be a sort of random
+ scratch field, for use by the back ends. The main gas code doesn't
+ do anything but initialize it to zero. The use of it does need to
+ be coordinated between the cpu and format files, though. E.g., some
+ coff targets pass the `addend' field from the cpu file via this
+ field. I don't know why the `fx_offset' field above can't be used
+ for that; investigate later and document. KR */
+ valueT fx_addnumber;
+
+ /* The location of the instruction which created the reloc, used
+ in error messages. */
+ const char *fx_file;
+ unsigned fx_line;
+
+#ifdef USING_CGEN
+ struct {
+ /* CGEN_INSN entry for this instruction. */
+ const struct cgen_insn *insn;
+ /* Target specific data, usually reloc number. */
+ int opinfo;
+ /* Which ifield this fixup applies to. */
+ struct cgen_maybe_multi_ifield * field;
+ /* is this field is the MSB field in a set? */
+ int msb_field_p;
+ } fx_cgen;
+#endif
+
+#ifdef TC_FIX_TYPE
+ /* Location where a backend can attach additional data
+ needed to perform fixups. */
+ TC_FIX_TYPE tc_fix_data;
+#endif
+};
+
+typedef struct fix fixS;
+
+struct reloc_list
+{
+ struct reloc_list *next;
+ union
+ {
+ struct
+ {
+ symbolS *offset_sym;
+ reloc_howto_type *howto;
+ symbolS *sym;
+ bfd_vma addend;
+ } a;
+ struct
+ {
+ asection *sec;
+ asymbol *s;
+ arelent r;
+ } b;
+ } u;
+ const char *file;
+ unsigned int line;
+};