From: Mark Mitchell <mark@codesourcery.com>
To: Mark Mitchell <mark@codesourcery.com>,
binutils@sources.redhat.com, rdsandiford@googlemail.com
Subject: Re: Should MIPS .eh_frame be writable?
Date: Tue, 08 Sep 2009 18:59:00 -0000 [thread overview]
Message-ID: <4AA6A975.5090309@codesourcery.com> (raw)
In-Reply-To: <87bpll1dc5.fsf@firetop.home>
Richard Sandiford wrote:
> The relocations are only for the personality routines, right?
Yes.
> If so, then I think we should simply use an indirect encoding.
> I'll do a (gcc) patch.
That's clearly ideal; I wasn't sure if it was possible. But, it doesn't
solve the problem that there are versions of GCC out there generating
code that results in a read-write frame. I think it's bad if GAS marks
a section as read-only when it should know that it's not. Shouldn't GAS
check that it's really generating a read-only frame before setting the
read-only bit?
Thanks,
--
Mark Mitchell
CodeSourcery
mark@codesourcery.com
(650) 331-3385 x713
next prev parent reply other threads:[~2009-09-08 18:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-08 14:51 Mark Mitchell
2009-09-08 18:49 ` Richard Sandiford
2009-09-08 18:59 ` Mark Mitchell [this message]
2009-09-08 19:50 ` Richard Sandiford
2009-09-08 20:24 ` Mark Mitchell
2009-09-09 21:16 ` Richard Sandiford
2009-09-09 23:44 ` Mark Mitchell
2009-09-10 7:56 ` Richard Sandiford
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AA6A975.5090309@codesourcery.com \
--to=mark@codesourcery.com \
--cc=binutils@sources.redhat.com \
--cc=rdsandiford@googlemail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).