Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@zwingli.cygnus.com>
To: fnf@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: another tweak to an init_types() call
Date: Sun, 09 Dec 2001 19:07:00 -0000	[thread overview]
Message-ID: <npd71n3h6o.fsf@zwingli.cygnus.com> (raw)
In-Reply-To: Fred Fish's message of Sun, 9 Dec 2001 11:06:20 -0700 (MST)


Approved.

Fred Fish <fnf@ns1.ninemoons.com> writes:

> 
> The build_gdbtypes() function in gdbtypes.c has another instance of
> where init_type() is called with empty flag bits and then a flag bit
> is set on the newly created type.  This patch fixes it, like in the
> similar c-lang.c patch approved and applied yesterday.
> 
> -Fred
> 
> 
> 2001-12-09  Fred Fish  <fnf@redhat.com>
> 
> 	* gdbtypes.c (build_gdbtypes): For builtin_type_char, pass
> 	TYPE_FLAG_NOSIGN to init_type() rather than setting it after the
> 	type is created.
> 
> Index: gdbtypes.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/gdbtypes.c,v
> retrieving revision 1.29
> diff -u -p -r1.29 gdbtypes.c
> --- gdbtypes.c	2001/12/07 22:11:51	1.29
> +++ gdbtypes.c	2001/12/09 18:07:25
> @@ -2939,9 +2937,8 @@ build_gdbtypes (void)
>  	       "void", (struct objfile *) NULL);
>    builtin_type_char =
>      init_type (TYPE_CODE_INT, TARGET_CHAR_BIT / TARGET_CHAR_BIT,
> -	       0,
> +	       TYPE_FLAG_NOSIGN,
>  	       "char", (struct objfile *) NULL);
> -  TYPE_FLAGS (builtin_type_char) |= TYPE_FLAG_NOSIGN;
>    builtin_type_true_char =
>      init_type (TYPE_CODE_CHAR, TARGET_CHAR_BIT / TARGET_CHAR_BIT,
>  	       0,
> 


      reply	other threads:[~2001-12-10  3:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-09 10:13 Fred Fish
2001-12-09 19:07 ` 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=npd71n3h6o.fsf@zwingli.cygnus.com \
    --to=jimb@zwingli.cygnus.com \
    --cc=fnf@redhat.com \
    --cc=gdb-patches@sources.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