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]

-msep-data without -fPIC ?


Hello,

For an embedded mmu-less m68k target, I would like to generate code
that will always run at a fixed place in memory, thus not needing to be PIC,
but that would access a data+bss segment that could be anywhere in memory,
thus needing accesses to the data segment via %a5 and an offset table.

1.  Does that possibility already exist in gcc (I did not find it) ?
	-msep-data currently does PI-text + PI-data.
2.  If it does not exist, I plan to integrate it.
	- From which release or branch should I start ?
	  I'd like to work on something that is stable except for my changes.
	- How is it currently possible in the gcc internals to know if a
	  SYMBOL_REF points to the .text or .rodata segments ?

Philippe


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