Home | History | Annotate | Download | only in apriori

Lines Matching refs:sections

46    relocation sections that it fully handles.  Instead, apriori just sets their
151 INFO("Creating new ELF sections.\n");
219 changes in sizes and numbers of relocation sections is compiled in. Note
248 assign section numbers to the remaining sections.
257 fields of those sections that need resizing.
275 value for those sections that refer to other sections. For
277 sections, because if we modify the symbol table that a
381 /* Copy the sections and the section headers. */
421 /* Find various sections. */
426 INFO("Processing [%s]'s sections...\n", source->name);
433 we remove sections. Since we do not update source->shnum
434 (we can't, since we need to know the original number of sections
733 if (source->jmprel.sections != NULL) {
734 destroy_range_list(source->jmprel.sections);
735 source->jmprel.sections = NULL;
737 if (source->rel.sections != NULL) {
738 destroy_range_list(source->rel.sections);
739 source->rel.sections = NULL;
813 out which relocation sections fit in which range as described by
1404 INFO("Prelinking [%s] (number of relocation sections: %d)%s...\n",
1478 /* Now prelink those relocation sections which were fully handled, and
1481 scanning source->shdr_info[] and looking for sections with idx == 0.
1486 relocation sections. prelink() those sections as well.
1687 /* Go over the sections that belong to this dynamic range. */
1689 if (dyn->sections) {
1691 range_t *scns = get_sorted_ranges(dyn->sections, &num_scns);
1693 INFO("\tdynamic range %s:[%lld, %lld) contains %d sections.\n",
1763 sections for removal. At this point, next is the section
1802 of the section header. When we create the new sections' data,
1809 new sections. The only sections for which we haven't
1810 created data are the relocation sections we are removing.
1855 } /* if (dyn->sections) */
1857 /* The dynamic entry won't have any sections when it itself doesn't
1858 exist. This could happen when we remove all relocation sections
1891 which relocation sections fit in which range as described by the
1931 if (NULL == source->rel.sections) {
1932 source->rel.sections = init_range_list();
1933 ASSERT(source->rel.sections);
1935 add_unique_range_nosort(source->rel.sections,
1964 if (NULL == source->jmprel.sections) {
1965 source->jmprel.sections = init_range_list();
1966 ASSERT(source->jmprel.sections);
1968 add_unique_range_nosort(source->jmprel.sections,
1990 if (source->rel.sections) sort_ranges(source->rel.sections);
1991 if (source->jmprel.sections) sort_ranges(source->jmprel.sections);
1996 INFO("We are dropping some sections from [%s]--creating section entries "
1997 "only for remaining sections.\n",
1999 /* Renumber the sections. The numbers for the sections after those we are
2000 dropping will be shifted back by the number of dropped sections. */
2057 sections we are removing. adjust_elf has an assertion that makes
2134 this is almost next the case. A file will often have sections
2137 the biggest sections that will not get loaded, which are the
2138 varios DWARF sections, all of which of which are named starting
2179 various relocation information sections are stored. */
2275 which we can shrink the various relocation sections before we
2276 call adjust_elf. After we've adjusted the sections, we will
2302 /* Find out the new section sizes of the relocation sections,
2318 their relocation sections, and adjust the size of those
2319 relocation sections. In the case when a relocation section
2343 and optionally marks sections for removal.
2368 INFO("All sections remain in [%s]--we are changing at "
2400 source->shnum, // number of sections in file
2404 drop_some_sections, // some sections are being dropped