From: Jakub Jelinek <jakub@redhat.com>
To: Tristan Gingold <gingold@adacore.com>
Cc: Chris Quenelle <chris.quenelle@oracle.com>, binutils@sourceware.org
Subject: Re: Sun/Oracle C++ compiler patch
Date: Fri, 25 Feb 2011 12:19:00 -0000 [thread overview]
Message-ID: <20110225121917.GK13037@sunsite.ms.mff.cuni.cz> (raw)
In-Reply-To: <50CDB2D0-36A5-48E2-94FE-91F7032F5B0A@adacore.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
next prev parent reply other threads:[~2011-02-25 12:19 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 [this message]
2011-02-25 18:11 ` Chris Quenelle
2011-04-01 3:13 ` Chris Quenelle
2011-04-11 15:40 ` Nick Clifton
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=20110225121917.GK13037@sunsite.ms.mff.cuni.cz \
--to=jakub@redhat.com \
--cc=binutils@sourceware.org \
--cc=chris.quenelle@oracle.com \
--cc=gingold@adacore.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).