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.  (Actually, there is some documentation
  28 in doc/as.texinfo, but it's *way* out of date.)
  29
  30 The documentation should also contain a "Trouble" section similar to gcc's
  31 manual: real bugs, common problems, incompatibilities, etc.
  32
  33 Anyone want to offer to maintain a man page?
  34
  35 BFD CONVERSION:
  36
  37 The "#ifdef BFD_ASSEMBLER" code is on its way in; the "#ifndef BFD_ASSEMBLER"
  38 code is on its way out.  The new code uses BFD data structures, and calls BFD
  39 for anything that needs to be written to the output file.  The old code did all
  40 the writing itself, or in a couple of cases, used BFD as a slightly higher
  41 level than stdio (i.e., bfd_seek, bfd_write -- these are not the preferred
  42 interface).
  43
  44 Because of this, some of this code is messy.  Lots of ifdef's, and the
  45 non-BFD_ASSEMBLER version often has multiple conditional tests inside it for
  46 various processors or formats.  As the various targets get converted over,
  47 these will gradually go away.
  48
  49 As of the moment I'm editing this file, only the "sun4" and "decstation-bsd"
  50 targets can really use the BFD code.  Other back ends still need merging or
  51 touching up.
  52
  53 TO DO:
  54
  55 Remove DONTDEF code, commented-out code.
  56
  57 Eliminate, as much as possible, anything not in config that is conditionalized
  58 on a CPU, format, or environment.
  59
  60 Merge COFF support into one version, supporting all the pseudo-ops used in
  61 either versions now, but using BFD for high-level operations.  (See second
  62 following item.)  Currently there are two versions (plus the new BFD code),
  63 which support different features, and are used on different targets.
  64
  65 Convert remaining a.out/b.out targets to using the BFD_ASSEMBLER code by
  66 default.
  67
  68 Finish conversion to using BFD for all object file writing.  (This is the
  69 BFD_ASSEMBLER code, not BFD or BFD_HEADERS.)  VMS might be the tough one here,
  70 since there's no BFD support for it at all yet.  Eliminate the old code.  Some
  71 of this can be done target by target, so doing a target where the CPU or
  72 format already supports BFD_ASSEMBLER mode may be easiest.
  73
  74 Fix lots of uses of empty strings to use null pointers.  Will improve
  75 efficiency, and should make code clearer too.
  76
  77 Clean up comments; lots of 'em are one previous maintainer griping about
  78 another previous maintainer, unrelated to the code.  (And with no names,
  79 they're not so fun to read. :-)
  80
  81 Get Steve to document H8/500 stuff (and others).
  82
  83 Improve test suite.  Incorporate more reported net bugs, and non-confidential
  84 Cygnus customer bugs, and anything else.
  85
  86 Add support for i386/i486 16-bit mode, so operating system initialization code
  87 doesn't require a separate assembler nor lots of `.byte' directives.
  88
  89 See if it's more maintainable (and not too much of a performance loss) to use
  90 a yacc grammar for parsing input.  The lexer will have to be flexible, and the
  91 grammar will have to contain any construct used on any platform, but it may be
  92 easier to maintain, instead of having code in most of the back ends.
  93
  94 PIC support.
  95
  96 (From old "NOTES" file to-do list, not really reviewed:)
  97
  98 fix relocation types for i860, perhaps by adding a ref pointer to fixS?
  99
 100 remove the ifdef's from fx_callj tests?
 101
 102 space tighten sparc alignment?
 103
 104 md_ => tc_
 105
 106 share b.out with a.out.