This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: Sun/Oracle C++ compiler patch
- From: Jakub Jelinek <jakub at redhat dot com>
- To: Tristan Gingold <gingold at adacore dot com>
- Cc: Chris Quenelle <chris dot quenelle at oracle dot com>, binutils at sourceware dot org
- Date: Fri, 25 Feb 2011 13:19:17 +0100
- Subject: Re: Sun/Oracle C++ compiler patch
- References: <4D66F521.8010902@oracle.com> <50CDB2D0-36A5-48E2-94FE-91F7032F5B0A@adacore.com>
- Reply-to: Jakub Jelinek <jakub at redhat dot com>
On Fri, Feb 25, 2011 at 10:54:32AM +0100, Tristan Gingold wrote:
>
> On Feb 25, 2011, at 1:17 AM, Chris Quenelle wrote:
>
> > (ignore the last copy of this email, it had a terrible subject line)
> >
> > Hello,
> >
> > When the Sun/Oracle C++ compiler was ported to Linux, we started
> > bundling a patched version of gnu ld to get the necessary treatment
> > for our exception range sections. I don't believe anyone has tried to
> > offer this patch upstream, and it would really help us out if we could
> > use the system linker when running on Linux. I've included the
> > contents of the patch at the end of this email.
>
> Just a suggestion: can you add a comment just before to explain that this is for Sun/Oracle C++ compiler ? This is not
> obvious from the section name.
>
> Is the content of this section documented somewhere ?
Also, do you really need ONLY_IF_R{O,W}, i.e. do some older Oracle C++ compiler versions
emit the section writable and some later compilers emit it read-only (or vice versa)?
.eh_frame with very old gcc versions used to be a writable sections that needed
runtime relocation, then gcc changed to a new format which doesn't need any relocations
and thus it is desirable to put the section into a read-only segment if all
.eh_frame input sections are read-only.
Jakub