Lines Matching defs:new
35 these entry points when creating a new BFD back end, since
101 When writing the linker routines for a new back end, you will
103 you have finished. You should simply create a new hash table
264 creating a new hash table.
873 /* Create a new entry for an archive hash table. */
942 re-search the symbol table each time a new object file was added.
957 number is incremented each time a new object file is included. The
958 pass number is used because when a new object file is included it
959 may create new undefined symbols which cause a previously examined
1377 linker is switched to the new version. */
1452 /* current\prev new undef undefw def defw com indr warn */
1608 /* Make a new undefined symbol. */
1615 /* Make a new weak undefined symbol. */
1658 character there, in case a new object file format
1681 for the new symbol. Fortunately, this case
2611 /* Allocate a new link_order for a section. */
2617 struct bfd_link_order *new;
2619 new = bfd_zalloc (abfd, amt);
2620 if (!new)
2623 new->type = bfd_undefined_link_order;
2626 section->map_tail.link_order->next = new;
2628 section->map_head.link_order = new;
2629 section->map_tail.link_order = new;
2631 return new;