From: Kevin Buettner <kevinb@redhat.com>
To: Jim Blandy <jimb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH RFA/RFC] Short pointer support
Date: Mon, 14 Oct 2002 18:01:00 -0000 [thread overview]
Message-ID: <1021015010133.ZM3115@localhost.localdomain> (raw)
In-Reply-To: Jim Blandy <jimb@redhat.com> "Re: [PATCH RFA/RFC] Short pointer support" (Oct 14, 3:45pm)
On Oct 14, 3:45pm, Jim Blandy wrote:
> It would be nice if we actually checked the pointer size against the
> correct size of short pointers on the target. There's something that
> feels a little flimsy about the way the patch just marks any pointer
> with a non-standard size with TYPE_FLAG_SHORTPTR. Wouldn't it be more
> robust to have an arch method that takes a non-standard pointer size,
> and returns the appropriate type flags for that, or zero if it's
> something it doesn't recognize? Or whatever.
Okay, this patch is withdrawn. I'm in the process of redoing it so
that it's more general and more robust.
Kevin
prev parent reply other threads:[~2002-10-15 1:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-11 14:26 Kevin Buettner
2002-10-12 1:57 ` Eli Zaretskii
2002-10-14 14:02 ` Jim Blandy
2002-10-14 18:01 ` Kevin Buettner [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=1021015010133.ZM3115@localhost.localdomain \
--to=kevinb@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@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