> >SHF_WRITE This section contains data that should be writable during >process > execution. > >SHF_ALLOC This section occupies memory during process execution. Some >con‐ > trol sections do not reside in the memory image of an >object > file. This attribute is off for those sections. > >SHF_EXECINSTR This section contains executable machine instructions. > >SHF_MASKPROC All bits included in this mask are reserved for >processor-spe‐ > cific semantics. > >So we can see that the ELF format does provide explicit flags for X and A.
Yes, ELF does provide X and A. I don't disagree. And Yes, they directly map to 'CODE' and 'ALLOC' flags printed by objdump. Sections: Idx Name Size VMA LMA File off Algn 0 .text 000000ca 00000000 00000000 00000094 2**1 CONTENTS, ALLOC, LOAD, READONLY, CODE 1 .bss 00000002 00800100 00800100 0000015e 2**0 ALLOC But the flags that ELF does not specify are - 'CONTENTS' and 'LOAD'. These are BFD specific flags. Objdump program computes and prints them in section headers regardless of the object file format type (mostly). So, even if we are dumping ELF sections, objdump prints certain flags which are not directly specified by ELF. This is the point I am referring to. Hopefully I am clear. Anitha _______________________________________________ AVR-GCC-list mailing list AVR-GCC-list@nongnu.org https://lists.nongnu.org/mailman/listinfo/avr-gcc-list