From: Roman Lechtchinsky <rl@cs.tu-berlin.de>
To: Richard Henderson <rth@redhat.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Reentering sections
Date: Wed, 26 Sep 2001 05:14:00 -0000 [thread overview]
Message-ID: <Pine.SOL.4.10.10109261405560.27267-100000@sossusvlei> (raw)
In-Reply-To: <20010921103649.A1667@redhat.com>
On Fri, 21 Sep 2001, Richard Henderson wrote:
> > Is this behavior actually necessary (the entire function body is
> > output before output_function_exception_table is called, AFAICS) or is the
> > call to function_section bogus?
>
> As currently configured, we have yet to do assemble_end_function,
> which does need to be in function_section.
> [...]
> It should be possible to rearrange this based on IA64_UNWIND_INFO.
Yep, there is one more problem, though. (*debug_hooks->function_decl) is
called after output_function_exception_table, but it needs to be in the
function section. Can it be output directly after assemle_end_function,
i.e. before the exception table on non-IA64_UNWIND_INFO architectures?
Bye
Roman
next prev parent reply other threads:[~2001-09-26 5:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-21 5:22 Roman Lechtchinsky
2001-09-21 10:36 ` Richard Henderson
2001-09-26 5:14 ` Roman Lechtchinsky [this message]
2001-09-26 12:46 ` Richard Henderson
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=Pine.SOL.4.10.10109261405560.27267-100000@sossusvlei \
--to=rl@cs.tu-berlin.de \
--cc=gcc@gcc.gnu.org \
--cc=rth@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).