gas/NOTES

   1 -*- text -*-
   2
   3 PORTING:
   4
   5 Sorry, no description of the interfaces is written up yet.  Look at existing
   6 back ends and work from there.
   7
   8 New hosts: If your host system has a strange header file setup, create a
   9 config/ho-foo.h file for it and include the appropriate header files or
  10 definitions there.  If your host has a broken compiler, or some broken macros
  11 in header files, create a host-specific file and repair the damage there.
  12 (See, for example, ho-rs6000.h.  The "assert" macro on that system doesn't work
  13 right, and a flag is set to rewrite an expression in tc-m68k.c that the native
  14 compiler mis-compiles.)
  15
  16 New target formats: Look at the BFD_ASSEMBLER code.  The a.out code might be a
  17 fair example.  There are no "good" examples yet, unfortunately, nor any good
  18 documentation of the changes.
  19
  20 New target processors: Check first to see if the BFD_ASSEMBLER interface is
  21 supported by the file format code you need to use.
  22
  23 New environments: ???
  24
  25 DOCUMENTATION:
  26
  27 The internals of gas need documenting.
  28
  29 Roland's going to work on removing the m4 processing from the user
  30 documentation.  With the latest texinfo code, it's not needed.
  31
  32 Anyone want to offer to maintain a man page?
  33
  34 BFD CONVERSION:
  35
  36 The "#ifdef BFD_ASSEMBLER" code is on its way in; the "#ifndef BFD_ASSEMBLER"
  37 code is on its way out.  The new code uses BFD data structures, and calls BFD
  38 for anything that needs to be written to the output file.  The old code did all
  39 the writing itself, or in a couple of cases, used BFD as a slightly higher
  40 level than stdio (i.e., bfd_seek, bfd_write -- these are not the preferred
  41 interface).
  42
  43 Because of this, some of this code is messy.  Lots of ifdef's, and the
  44 non-BFD_ASSEMBLER version often has multiple conditional tests inside it for
  45 various processors or formats.  As the various targets get converted over,
  46 these will gradually go away.
  47
  48 As of the moment I'm editing this file, only the "sun4" and "decstation-bsd"
  49 targets can really use the BFD code.  Other back ends still need merging or
  50 touching up.
  51
  52 TO DO:
  53
  54 Remove DONTDEF code, commented-out code.
  55
  56 Eliminate, as much as possible, anything not in config that is conditionalized
  57 on a CPU, format, or environment.
  58
  59 Finish conversion to using BFD for all object file writing.  (This is the
  60 BFD_ASSEMBLER code, not BFD or BFD_HEADERS.)  VMS might be the tough one here,
  61 since there's no BFD support for it at all yet.  Eliminate the old code.
  62
  63 Clean up comments; lots of 'em are one previous maintainer griping about
  64 another previous maintainer, unrelated to the code.  (And with no names,
  65 they're not so fun to read. :-)
  66
  67 Get Steve to document H8/500 stuff.
  68
  69 Put together a test suite, using DejaGnu.
  70
  71 (From old "NOTES" file to-do list, not really reviewed:)
  72
  73 fix relocation types for i860, perhaps by adding a ref pointer to fixS?
  74
  75 remove the ifdef's from fx_callj tests?
  76
  77 space tighten sparc alignment?
  78
  79 md_ => tc_
  80
  81 share b.out with a.out.