1 Things that still need to be done: -*- Text -*- 2 3 o - A source of space lossage is that all the target-dependent code 4 is in a single bfd_target structure. Hence all the code for 5 *writing* object files is still pulled into all the applications 6 that only care about *reading* (gdb, nm, objdump), while gas has 7 to carry along all the unneeded baggage for reading objects. And 8 so on. This would be a substantial change, and the payoff would 9 not all that great (essentially none if bfd is used as a shared 10 library). 11 12 o - The storage needed by BFD data structures is also larger than strictly 13 needed. This may be difficult to do much about. 14 15 o - implement bfd_abort, which should close the bfd but not alter the 16 filesystem. 17 18 o - update the bfd doc; write a how-to-write-a-backend doc, take out 19 the stupid quips and fill in all the blanks. 20 21 o - upgrade the reloc handling as per Steve's suggestion. 22 24 Copyright (C) 2012-2016 Free Software Foundation, Inc. 25 26 Copying and distribution of this file, with or without modification, 27 are permitted in any medium without royalty provided the copyright 28 notice and this notice are preserved. 29
