https://sourceware.org/bugzilla/show_bug.cgi?id=14406
--- Comment #2 from Georg-Johann Lay <gjl at gcc dot gnu.org> --- Created attachment 11148 --> https://sourceware.org/bugzilla/attachment.cgi?id=11148&action=edit Augmentation of default linker script. Link with -Tflash12.ld WON'T FIX this one: The layout of code and data highly depends on the requirements of a project, and supplying a default layout would most likely introduce assumptions that and not appropriate and would conflict with the assumptions of most projects. Hence, it's best not to introduce such assumptions and leave it up to the user to design code and data layout for a project if it uses __flashN. Basically, there are 2 appoaches: 1) Supply a project-specific linker script. 2) Augment the default linker script. Example: Suppose the application only needs __flash1 and / or __flash2, and the corresponding sections .progmem1.data, .progmem2.data should be located after .text, i.e. after all code, jumptables and data from __memx but before the initializers for .data. Then you can augment the default linker script by linking with -Tflash12.ld where flash12.ld is the attached text file. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
