This is the mail archive of the gcc-patches@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: [PATCH] Make .eh_frame and .gcc_except_table read-only if possible

From: Richard Henderson <rth at redhat dot com>
To: Jakub Jelinek <jakub at redhat dot com>
Cc: gcc-patches at gcc dot gnu dot org
Date: Mon, 25 Nov 2002 09:55:44 -0800
Subject: Re: [PATCH] Make .eh_frame and .gcc_except_table read-only if possible
References: <20021123214607.R14760@sunsite.ms.mff.cuni.cz> <20021124044240.GA14432@redhat.com> <20021125102940.U27455@devserv.devel.redhat.com>

On Mon, Nov 25, 2002 at 10:29:40AM -0500, Jakub Jelinek wrote:
> Argh, just tested it. Don't see any sense in the apparent rule
> "if any input section is read-only, output is read-only,
> otherwise read-write" which Solaris ld uses.

Err, the rule I saw is that the ro sections got placed in the
ro segment and the rw sections got placed in the rw segment.
I.e. not all of the same-name sections were placed sequentially.

r~

Follow-Ups:
- [PATCH] Make .eh_frame and .gcc_except_table read-only if possible (take 3)
  - From: Jakub Jelinek

References:
- [PATCH] Make .eh_frame and .gcc_except_table read-only if possible
  - From: Jakub Jelinek
- Re: [PATCH] Make .eh_frame and .gcc_except_table read-only if possible
  - From: Richard Henderson
- Re: [PATCH] Make .eh_frame and .gcc_except_table read-only if possible
  - From: Jakub Jelinek

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