section names inconsistencies

Discussion about Parallella (and Epiphany) Software Development

Moderators: amylaar, jeremybennett, simoncook

section names inconsistencies

Postby notzed » Sun Nov 03, 2013 11:57 pm

This isn't a big issue but it would be nice if the section names from the sdk were a bit more consistent and fitted with existing toolchain conventions.

Specifically ...

IVT_RESET, ivt_entry_software_exception, etc ...; they don't specify .text sections, and the names are inconsistent (and even renamed in the linker script)

workgroup_cfg, ext_mem_cfg; they don't specify .data sections, and are renamed in the normal linker script?

text_bankN, data_bankN; they should be .text.bankN, .data.bankN (and add .bss.bankN) to indicate their type.

code_dram; what is it? code? data? How is it different to shared_dram? Overall a bit confusing, no types are specified and doesn't handle bss either.

Having the wrong section types (i.e. .text, .data, .bss prefixes) means objdump isn't as useful as it could be for example.
notzed
 
Posts: 331
Joined: Mon Dec 17, 2012 12:28 am
Location: Australia

Return to Programming Q & A

Who is online

Users browsing this forum: No registered users and 55 guests