From: Paul Mackerras <paulus@samba.org>
To: davidm@hpl.hp.com
Cc: Andrew Morton <akpm@osdl.org>,
Jes Sorensen <jes@trained-monkey.org>,
linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org
Subject: Re: [patch] 2.6.1-mm5 compile do not use shared extable code for
Date: Sat, 24 Jan 2004 10:49:26 +0000 [thread overview]
Message-ID: <16402.19894.686335.695215@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <16401.57298.175645.749468@napali.hpl.hp.com>
David Mosberger writes:
> How about something along these lines? If you want to standardize on
> a single instruction-address format, I'd strongly favor using the
> location-relative addresses used on Alpha and ia64 (it makes no sense
> to uses a full 64-bit address for those members).
Won't you have to change the offset when you move the entry, if the
value you store is relative to the address of the entry? You could
get around that by storing the offset relative to the start of the
exception table, I guess.
Paul.
next prev parent reply other threads:[~2004-01-24 10:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 12:23 [patch] 2.6.1-mm5 compile do not use shared extable code for ia64 Jes Sorensen
2004-01-20 17:00 ` [patch] 2.6.1-mm5 compile do not use shared extable code for Andrew Morton
2004-01-24 3:00 ` David Mosberger
2004-01-24 10:49 ` Paul Mackerras [this message]
2004-01-26 23:33 ` David Mosberger
2004-01-27 8:11 ` [patch] 2.6.1-mm5 compile do not use shared extable code for ia64 Jes Sorensen
2004-01-27 17:39 ` David Mosberger
2004-01-27 8:56 ` [patch] 2.6.1-mm5 compile do not use shared extable code for Paul Mackerras
2004-01-27 16:19 ` David Mosberger
2004-01-27 23:49 ` Paul Mackerras
2004-01-28 6:06 ` David Mosberger
2004-01-27 17:54 ` David Mosberger
2004-01-21 18:43 ` [patch] 2.6.1-mm5 compile do not use shared extable code for ia64 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=16402.19894.686335.695215@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=akpm@osdl.org \
--cc=davidm@hpl.hp.com \
--cc=jes@trained-monkey.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@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