From: Richard Henderson <rth@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: "H.J. Lu" <hjl.tools@gmail.com>,
Ian Lance Taylor <iant@google.com>,
Ulrich Weigand <uweigand@de.ibm.com>,
Andrew Pinski <pinskia@gmail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: PATCH: PR other/48007: Unwind library doesn't work with UNITS_PER_WORD > sizeof (void *)
Date: Wed, 23 Mar 2011 18:20:00 -0000 [thread overview]
Message-ID: <4D8A39E8.30204@redhat.com> (raw)
In-Reply-To: <20110323180437.GP18914@tyan-ft48-01.lab.bos.redhat.com>
On 03/23/2011 11:04 AM, Jakub Jelinek wrote:
> For several targets that would grow the context significantly, do you think
> we really have to do that for all targets rather than just for the
> sizeof (_Unwind_Word) > sizeof (void *) ones? The accessors are wrapped
> in inline functions anyway.
Given that ia64 doesn't use this file, we're talking about 512 bytes for
most 64-bit targets. I suppose that's 512 bytes we needn't allocate for
others, but...
The problem is that we suddenly have a version mismatch. Suppose we
conditionally add this, then next decade we need to add some other field
unconditionally. Now determining what version X means is non-trivial.
What targets are you worried most about?
r~
next prev parent reply other threads:[~2011-03-23 18:20 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-06 17:18 H.J. Lu
2011-03-06 21:15 ` Andrew Pinski
2011-03-06 21:28 ` H.J. Lu
2011-03-06 23:23 ` Richard Guenther
2011-03-06 23:40 ` H.J. Lu
2011-03-07 0:15 ` H.J. Lu
2011-03-14 17:49 ` H.J. Lu
2011-03-21 21:56 ` Ian Lance Taylor
2011-03-22 4:19 ` H.J. Lu
2011-03-22 6:32 ` Ian Lance Taylor
2011-03-22 15:19 ` Ulrich Weigand
2011-03-22 15:41 ` Jakub Jelinek
2011-03-22 16:42 ` Ian Lance Taylor
2011-03-22 16:52 ` Andrew Pinski
2011-03-22 18:58 ` Ian Lance Taylor
2011-03-22 19:30 ` Ulrich Weigand
2011-03-22 22:18 ` Ian Lance Taylor
2011-03-23 3:25 ` H.J. Lu
2011-03-23 4:53 ` Ian Lance Taylor
2011-03-23 5:01 ` H.J. Lu
2011-03-23 13:58 ` Ian Lance Taylor
2011-03-23 17:50 ` Richard Henderson
2011-03-23 18:04 ` Jakub Jelinek
2011-03-23 18:20 ` Richard Henderson [this message]
2011-03-23 18:24 ` H.J. Lu
2011-03-23 18:27 ` Richard Henderson
2011-03-23 18:37 ` Jakub Jelinek
2011-03-23 19:01 ` Richard Henderson
2011-03-23 19:17 ` Jakub Jelinek
2011-03-23 19:22 ` Ulrich Weigand
2011-03-24 7:15 ` H.J. Lu
2011-04-10 1:52 ` 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=4D8A39E8.30204@redhat.com \
--to=rth@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=iant@google.com \
--cc=jakub@redhat.com \
--cc=pinskia@gmail.com \
--cc=uweigand@de.ibm.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).