From: "H. J. Lu" <hjl@lucon.org>
To: linux-ia64@vger.kernel.org
Subject: Re: PATCH: Don't allow ia64 unwind section to point to section in different files
Date: Mon, 16 May 2005 13:58:22 +0000 [thread overview]
Message-ID: <20050516135821.GA2538@lucon.org> (raw)
In-Reply-To: <20050513214612.GA31765@lucon.org>
On Mon, May 16, 2005 at 02:26:36AM -0700, David Mosberger wrote:
> >>>>> On Fri, 13 May 2005 14:58:15 -0700, "H. J. Lu" <hjl@lucon.org> said:
>
> HJ> Well, it isn't very useful. The problem is libc.a has many weak
> HJ> functions and user can override them. My patch will make it
> HJ> impossible on ia64. I guess we may have to live with the
> HJ> imperfect unwind info when weak functions are used. The unwinder
> HJ> may have to deal with it.
>
> Huh? How do you propose it deal with it?
>
> Wrong unwind info will break exception handling. I don't think that's
> acceptable.
Since the weak function is still in the executable, its unwind info is
also there. That is what you see in kernel.
H.J.
prev parent reply other threads:[~2005-05-16 13:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-13 21:46 PATCH: Don't allow ia64 unwind section to point to section in different files H. J. Lu
2005-05-13 21:58 ` H. J. Lu
2005-05-16 9:26 ` David Mosberger
2005-05-16 13:58 ` H. J. Lu [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=20050516135821.GA2538@lucon.org \
--to=hjl@lucon.org \
--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