Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "H. J. Lu" <hjl@lucon.org>
To: GDB <gdb-patches@sources.redhat.com>
Subject: Re: PATCH: Initialize tmp_obstack
Date: Tue, 05 Dec 2006 20:56:00 -0000	[thread overview]
Message-ID: <20061205205638.GA30432@lucon.org> (raw)
In-Reply-To: <20061205204003.GB25572@nevyn.them.org>

On Tue, Dec 05, 2006 at 03:40:03PM -0500, Daniel Jacobowitz wrote:
> On Sat, Dec 02, 2006 at 10:27:12AM -0800, H. J. Lu wrote:
> > Gcc 4.1 warns
> 
> Mine doesn't, but I never did figure out why some compilers do and
> others don't.
> 
> > 2006-12-02  H.J. Lu  <hongjiu.lu@intel.com>
> > 
> > 	* cp-valprint.c (cp_print_value_fields): Initialize tmp_obstack.
> > 	(cp_print_value): Likewise
> > 	* p-valprint.c (pascal_object_print_value_fields): Likewise
> > 	(pascal_object_print_value): Likewise
> 
> OK to commit - let's use this version.  Thanks.  I think it's fine for
> the 4.2 branch too.

I assume that you meant gdb 6.5 branch.


H.J.


  reply	other threads:[~2006-12-05 20:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-02 18:27 H. J. Lu
2006-12-05 20:40 ` Daniel Jacobowitz
2006-12-05 20:56   ` H. J. Lu [this message]
2006-12-05 21:00     ` Daniel Jacobowitz
     [not found]   ` <12601.163.1.150.229.1165354805.squirrel@webmail.xs4all.nl>
     [not found]     ` <20061205214306.GA29801@nevyn.them.org>
     [not found]       ` <20637.163.1.150.229.1165355320.squirrel@webmail.xs4all.nl>
2006-12-05 21:56         ` Daniel Jacobowitz
2006-12-05 21:59           ` Daniel Jacobowitz
2006-12-05 22:24             ` Jim Blandy
2006-12-05 23:58           ` Daniel Jacobowitz
2006-12-07 14:40             ` Daniel Jacobowitz
2006-12-25  4:00               ` Daniel Jacobowitz
2007-01-16  6:59                 ` Daniel Jacobowitz
2007-01-16 21:32                   ` Mark Kettenis
2007-01-21 13:07                   ` Mark Kettenis
2007-01-21 15:59                     ` Daniel Jacobowitz
2007-01-21 17:24                       ` Daniel Jacobowitz
2007-02-08 14:21                         ` Daniel Jacobowitz

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=20061205205638.GA30432@lucon.org \
    --to=hjl@lucon.org \
    --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