Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@codesourcery.com>
To: gdb-patches@sourceware.org
Subject: Re: RFA: don't swap void builtin type
Date: Wed, 06 Dec 2006 00:57:00 -0000	[thread overview]
Message-ID: <m3u009suvx.fsf@codesourcery.com> (raw)
In-Reply-To: <20061205205047.GE25572@nevyn.them.org> (Daniel Jacobowitz's message of "Tue, 5 Dec 2006 15:50:48 -0500")


Daniel Jacobowitz <drow@false.org> writes:
> On Mon, Dec 04, 2006 at 02:06:31PM -0800, Jim Blandy wrote:
>> 
>> I can't see any reason we need to swap out builtin_type_void while
>> changing architectures, and it is nice to have as many types available
>> in as many circumstances as possible.
>> 
>> gdb/ChangeLog:
>> 2006-12-04  Jim Blandy  <jimb@codesourcery.com>
>> 
>> 	* gdbtypes.c (built_gdbtypes): Don't set builtin_type_void here.
>> 	(_initialize_gdbtypes): Do it here, and don't swap it when the
>> 	architecture changes.
>> 
>
> OK.

Committed, thanks.


      reply	other threads:[~2006-12-06  0:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-04 22:05 Jim Blandy
2006-12-05 20:50 ` Daniel Jacobowitz
2006-12-06  0:57   ` Jim Blandy [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=m3u009suvx.fsf@codesourcery.com \
    --to=jimb@codesourcery.com \
    --cc=gdb-patches@sourceware.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