This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Variable order and location within the section - optimization level dependent
- From: Janáček Jiří <jiri dot janacek at skoda dot cz>
- To: "gcc-help at gcc dot gnu dot org" <gcc-help at gcc dot gnu dot org>
- Date: Wed, 16 Oct 2013 11:25:45 +0000
- Subject: Variable order and location within the section - optimization level dependent
- Authentication-results: sourceware.org; auth=none
Hello all,
We have discussed the topic regarding the compiler flag -fno-toplevel-reorder and relative stuff at the GCC ARM forum (https://answers.launchpad.net/gcc-arm-embedded/+question/237324).
GCC documentation (http://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html#Optimize-Options) states:
"Do not reorder top-level functions, variables, and asm statements. Output them in the same order that they appear in the input file. When this option is used, unreferenced static variables are not removed. This option is intended to support existing code that relies on a particular ordering. For new code, it is better to use attributes."
The major question sounds - which attributes should be applied in such a case?
Many thanks in advance,
Best regards,
JiriJ