From: Saul Tamari <stamari@gmail.com>
To: Ian Lance Taylor <iant@google.com>
Cc: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: Moving C++ code to a different ELF section
Date: Wed, 19 Feb 2014 18:21:00 -0000 [thread overview]
Message-ID: <CAGqvRw4+PwUKGf6TaoH12vR14PjimqH269X6SW-XcxMCOAZfFw@mail.gmail.com> (raw)
In-Reply-To: <CAKOQZ8z+BjeMKa4JmT+oXh29eyNoSQez42Cx6OnUv4nGEXDV0A@mail.gmail.com>
On Wed, Feb 19, 2014 at 12:45 PM, Ian Lance Taylor <iant@google.com> wrote:
[snip]
> OK, then I think your best path forward will be to modify the compiler
> to enhance that option to work with exception handling. I don't know
> of any fundamental reason why exception handling is incompatible with
> separate sections for hot and cold code, though it will likely require
> a modification to the way the exception frame information is generated
> (this is, as it happens, the same CFI information that you are getting
> errors on with your asm approach).
That would be quite a challenge for me as I have zero experience with
the gcc codebase.
> Or, of course, you can use different functions for the cold code,
> using the section attribute to put them in a different section, if
> that is workable.
That won't enable me to use it without extensive modifications to the
current code base.
Thanks,
Saul
prev parent reply other threads:[~2014-02-19 18:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 13:57 Saul Tamari
2014-02-19 14:11 ` Ian Lance Taylor
2014-02-19 15:15 ` Saul Tamari
2014-02-19 17:01 ` Ian Lance Taylor
2014-02-19 17:27 ` Saul Tamari
2014-02-19 17:45 ` Ian Lance Taylor
2014-02-19 18:21 ` Saul Tamari [this message]
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=CAGqvRw4+PwUKGf6TaoH12vR14PjimqH269X6SW-XcxMCOAZfFw@mail.gmail.com \
--to=stamari@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=iant@google.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).