This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] Make .eh_frame and .gcc_except_table read-only if possible (take 3)
- From: Jakub Jelinek <jakub at redhat dot com>
- To: David Edelsohn <dje at watson dot ibm dot com>
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Wed, 11 Dec 2002 16:14:55 -0500
- Subject: Re: [PATCH] Make .eh_frame and .gcc_except_table read-only if possible (take 3)
- References: <20021125151359.B27455@devserv.devel.redhat.com> <200212112111.QAA23634@makai.watson.ibm.com>
- Reply-to: Jakub Jelinek <jakub at redhat dot com>
On Wed, Dec 11, 2002 at 04:11:37PM -0500, David Edelsohn wrote:
> * configure.in (HAVE_LD_RO_RW_SECTION_MIXING): Check what ld does
> when linking read-only and read-write sections together.
>
> echo '.section "myfoosect", "a"' > conftest1.s
>
> The assembler directives in the test only make sense for ELF targets.
Yes.
Is there any other obj format which wants to move to read-only .eh_frame section?
If not, the test will on non-ELF just result in HAVE_LD_RO_RW_SECTION_MIXING
not being defined and thus keeping status quo.
Jakub