From: David Mosberger <davidm@napali.hpl.hp.com>
To: "H . J . Lu" <hjl@lucon.org>
Cc: davidm@hpl.hp.com, Ulrich Drepper <drepper@redhat.com>,
GNU libc hacker <libc-hacker@sources.redhat.com>,
binutils@sources.redhat.com
Subject: Re: [David Mosberger <davidm@hpl.hp.com>] problem with unwind info for .init/.fini sections
Date: Thu, 28 Feb 2002 17:43:00 -0000 [thread overview]
Message-ID: <15486.56491.696020.742674@napali.hpl.hp.com> (raw)
In-Reply-To: <20020228173311.A26728@lucon.org>
>>>>> On Thu, 28 Feb 2002 17:33:11 -0800, "H . J . Lu" <hjl@lucon.org> said:
HJ> I believe glibc is ok. The problem is binutils. I didn't see any
HJ> supports for DT_INIT_ARRAY, DT_FINI_ARRAY. DT_INIT_ARRAYSZ,
HJ> DT_FINI_ARRAYSZ, DT_PREINIT_ARRAY nor DT_PREINIT_ARRAYSZ.
Shouldn't this be easy straight-forward to add?
I guess the other component that needs updating is gcc (at least the
ia64 versions of crtbegin.asm and crtend.asm would need that). I'd be
happy to work on this.
--david
next prev parent reply other threads:[~2002-03-01 1:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-28 14:38 Ulrich Drepper
2002-02-28 16:58 ` H . J . Lu
2002-02-28 17:19 ` David Mosberger
2002-02-28 17:28 ` Ulrich Drepper
2002-02-28 17:33 ` H . J . Lu
2002-02-28 17:43 ` David Mosberger [this message]
[not found] ` <20020228175426.A30756@redhat.com>
2002-02-28 18:01 ` David Mosberger
2002-02-28 18:11 ` H . J . Lu
2002-02-28 22:42 ` David Mosberger
[not found] ` <20020228225757.A30933@redhat.com>
2002-03-01 10:24 ` David Mosberger
[not found] ` <20020301164725.C31581@redhat.com>
2002-03-01 16:56 ` David Mosberger
[not found] ` <20020301170010.A31610@redhat.com>
2002-03-01 17:20 ` David Mosberger
[not found] ` <20020301172558.A31648@redhat.com>
2002-03-01 17:36 ` David Mosberger
2002-03-02 0:36 ` H . J . Lu
[not found] ` <20020302101931.GM1059@bubble.sa.bigpond.net.au>
2002-03-02 9:24 ` David Mosberger
2002-03-02 10:59 ` H . J . Lu
2002-03-02 11:13 ` David Mosberger
2002-03-02 11:27 ` H . J . Lu
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=15486.56491.696020.742674@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=binutils@sources.redhat.com \
--cc=davidm@hpl.hp.com \
--cc=drepper@redhat.com \
--cc=hjl@lucon.org \
--cc=libc-hacker@sources.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).