diff options
author | Richard Henderson <rth@redhat.com> | 1999-05-03 07:29:11 +0000 |
---|---|---|
committer | Richard Henderson <rth@redhat.com> | 1999-05-03 07:29:11 +0000 |
commit | 252b5132c753830d5fd56823373aed85f2a0db63 (patch) | |
tree | 1af963bfd8d3e55167b81def4207f175eaff3a56 /bfd/TODO | |
download | binutils-252b5132c753830d5fd56823373aed85f2a0db63.zip binutils-252b5132c753830d5fd56823373aed85f2a0db63.tar.gz binutils-252b5132c753830d5fd56823373aed85f2a0db63.tar.bz2 |
19990502 sourceware importbinu_ss_19990502
Diffstat (limited to 'bfd/TODO')
-rw-r--r-- | bfd/TODO | 25 |
1 files changed, 25 insertions, 0 deletions
diff --git a/bfd/TODO b/bfd/TODO new file mode 100644 index 0000000..7a12735 --- /dev/null +++ b/bfd/TODO @@ -0,0 +1,25 @@ +Things that still need to be done: -*- Text -*- + + o - A source of space lossage is that all the target-dependent code + is in a single bfd_target structure. Hence all the code for + *writing* object files is still pulled into all the applications + that only care about *reading* (gdb, nm, objdump), while gas has + to carry along all the unneeded baggage for reading objects. And + so on. This would be a substantial change, and the payoff would + not all that great (essentially none if bfd is used as a shared + library). + + o - The storage needed by BFD data structures is also larger than strictly + needed. This may be difficult to do much about. + + o - implement bfd_abort, which should close the bfd but not alter the + filesystem. + + o - update the bfd doc; write a how-to-write-a-backend doc, take out + the stupid quips and fill in all the blanks. + + o - upgrade the reloc handling as per Steve's suggestion. + + + + |