From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] problem with unwind info for .init/.fini sections
Date: Thu, 28 Feb 2002 21:33:39 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905203@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905179@msgid-missing>
>>>>> On Wed, 27 Feb 2002 11:19:30 -0800, Cary Coutant <cary@cup.hp.com> said:
>> I can think of two approaches:
>> ...
>> Anybody else have a better idea or other comments?
Cary> (3) Use the .init_array and .fini_array sections instead.
This would be by far the cleanest solution.
How well is this supported in binutils at the moment? I see some
references to it, but am not sure whether there are any holes in its
support.
Are there any reasons *not* to switch to .init_array/.fini_array as
the primary init/fini mechanism? Besides fixing the unwind problem,
it seems to me it's generally just a much cleaner solution and should
allow us to get rid of some rather ugly hacks in glibc.
--david
next prev parent reply other threads:[~2002-02-28 21:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-22 19:54 [Linux-ia64] problem with unwind info for .init/.fini sections David Mosberger
2002-02-27 19:19 ` Cary Coutant
2002-02-28 12:02 ` [Linux-ia64] problem with unwind info for .init/.fini section Zagorodnev, Grigory
2002-02-28 21:33 ` David Mosberger [this message]
2002-02-28 21:47 ` David Mosberger
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=marc-linux-ia64-105590701905203@msgid-missing \
--to=davidm@hpl.hp.com \
--cc=linux-ia64@vger.kernel.org \
/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