Lines Matching full:section
53 # Update the ranges entry for the given module 'mod' in section 'osect'.
57 # section data, and the first module may very well start at the same address.
85 # (2) Collect address information for each section.
89 # We collect the base address of the section in order to convert all addresses
90 # in the section into offset values.
92 # We collect the address of the anchor (or first symbol in the section if there
94 # ranges based on the actual load address of the section in the running kernel.
96 # We collect the start address of any sub-section (section included in the top
97 # level section being processed). This is needed when the final linking was
99 # section is to be obtained from vmlinux.o.map. The offset of the sub-section
117 # (LLD) Convert a section record fronm lld format to ld format.
152 # We only care about these while processing a section for which no anchor has
169 # (LD) Section records with just the section name at the start of the line
171 # loadable section. If it is, the next line will contains a hex value
183 # (LD) Object records with just the section name denote records with a long
184 # section name for which the remainder of the record can be found on the
195 # Beginning a new section - done with the previous one (if any).
201 # Process a loadable section (we only care about .-sections).
203 # Record the section name and its base address.
204 # We also record the raw (non-stripped) address of the section because it can
239 # If we are not in a section we care about, we ignore the record.
245 # Record the first anchor symbol for the current section.
247 # An anchor record for the section bears the same raw address as the section
260 # If no anchor record was found for the current section, use the first symbol
261 # in the section as anchor.
276 # The first occurrence of a section name in an object record establishes the
277 # addend (often 0) for that section. This information is needed to handle
281 # If the section does not have a base yet, use the base of the encapsulating
282 # section.
307 # (3) Collect offset ranges (relative to the section base address) for built-in
311 # the information we need (see section (3a)).
313 # vmlinux.o.map (see section (3b)).
317 # Since we are already processing vmlinux.map, the top level section that is
337 # Turn the address into an offset from the section base.
350 # + If we are still processing within the same main section, we
354 # + Otherwise, we validate the end offset against the section
397 # (3) Collect offset ranges (relative to the section base address) for built-in
417 # If we do not know an addend for the object's section, we are interested in
418 # anything within that section.
420 # Determine the top-level section that the object's section was included in
421 # during the final link. This is the section name offset range data will be
432 # We need to work with the main section.
435 # Turn the address into an offset from the section base.
448 # + If we are still processing within the same main section, we
452 # + Otherwise, we validate the end offset against the section
489 # Anchor records are added for each section that contains offset range data
490 # records. They are added at an adjusted section base address (base << 1) to