From: Daniel Jacobowitz <drow@false.org>
To: Jim Blandy <jimb@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Now I know why we used to swap builtin_type_void.
Date: Wed, 06 Dec 2006 20:07:00 -0000 [thread overview]
Message-ID: <20061206200655.GA9791@nevyn.them.org> (raw)
In-Reply-To: <m33b7srds8.fsf@codesourcery.com>
On Wed, Dec 06, 2006 at 12:05:11PM -0800, Jim Blandy wrote:
> Why doesn't the same logic apply to the other types created in
> _initialize_gdbtypes? I believe they're never referred to by debug
> information, and the user has no way to refer to them from the command
> line, so that keeps us out of trouble in those cases. But if some
> architecture-specific code ever calls lookup_pointer_type on them,
> won't we have the same problem you've discovered above with void?
Exactly. I think we'd have to move TYPE_POINTER_TYPE out of the type
and into e.g. an architecture hash table to fix this. Worth it?
Don't know.
> I'll revert the patch. It was just a cleanup; I don't actually need
> it for anything.
Thanks.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-12-06 20:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-06 19:52 Daniel Jacobowitz
2006-12-06 20:04 ` Jim Blandy
2006-12-06 20:07 ` Daniel Jacobowitz [this message]
2006-12-06 20:15 ` Jim Blandy
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=20061206200655.GA9791@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=jimb@codesourcery.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