From: Nick Clifton <nickc@redhat.com>
To: Chris Quenelle <chris.quenelle@oracle.com>
Cc: Jakub Jelinek <jakub@redhat.com>,
Tristan Gingold <gingold@adacore.com>,
binutils@sourceware.org
Subject: Re: Sun/Oracle C++ compiler patch
Date: Mon, 11 Apr 2011 15:40:00 -0000 [thread overview]
Message-ID: <4DA320D4.6070300@redhat.com> (raw)
In-Reply-To: <4D9542BB.8080804@oracle.com>
Hi Chris,
> I'm not really sure that the "ONLY_IF_RW" in the linker script maps onto
> the sh_flags field having the SHF_WRITE bit turned on in the section
> header table. Could you confirm that?
It does.
> Currently our exception range sections are writable, but I haven't been
> able to confirm that's necessary because of fixups by the C++ runtime
> system. If it's not necessary or if we change it later, it would be
> nice if the linker didn't need more modification.
Agreed.
> Is there any harm in allowing the same behavior if our sections later
> become read-only?
None.
> .gcc_except_table ${RELOCATING-0} : ONLY_IF_RO { *(.gcc_except_table
> .gcc_except_table.*) }
> + .exception_ranges ${RELOCATING-0} : ONLY_IF_RO { *(.exception_ranges
> .exception_ranges*) }
> .gcc_except_table ${RELOCATING-0} : ONLY_IF_RW { *(.gcc_except_table
> .gcc_except_table.*) }
> + .exception_ranges ${RELOCATING-0} : ONLY_IF_RW { *(.exception_ranges
> .exception_ranges*) }
The patch looks OK to me, and so I have checked it in along with this
changelog entry. I did take Tristan's suggestion however and so I added
a comment explaining where the .exception_ranges section originates.
Cheers
Nick
ld/ChangeLog
2011-04-11 Chris Quenelle <chris.quenelle@oracle.com>
* scripttempl/elf.sc (.exception_ranges): Add new section.
next prev parent reply other threads:[~2011-04-11 15:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-25 0:17 Chris Quenelle
2011-02-25 9:54 ` Tristan Gingold
2011-02-25 12:19 ` Jakub Jelinek
2011-02-25 18:11 ` Chris Quenelle
2011-04-01 3:13 ` Chris Quenelle
2011-04-11 15:40 ` Nick Clifton [this message]
2011-04-12 21:49 ` Chris Quenelle
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=4DA320D4.6070300@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=chris.quenelle@oracle.com \
--cc=gingold@adacore.com \
--cc=jakub@redhat.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).