This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: CONSTANT_POOL_BEFORE_FUNCTION has no effect in tm.h?


The target doesn't use ELF. I have .text, .data, and .bss, and
read-only data normally goes in .text. I'm learning as I go, so I'll
fiddle with a dummy .rodata section of some sort that the linker can
position accordingly.

On Mon, Jul 6, 2009 at 10:00 AM, Ian Lance Taylor<iant@google.com> wrote:
> Most targets put constant strings and the like in the .rodata section.
> Then the linker script can put that in a useful place. ?That seems like
> the best approach to use for a processor like m68k which supports
> general addressing. ?I'm surprised that doesn't happen already. ?I
> assume you are using an ELF target, in which case I would expect
> default_elf_select_rtx_section to do the right thing.
>
> Ian
>


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]