From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: Jim Blandy <jimb@codesourcery.com>,
Markus Deuling <deuling@de.ibm.com>,
Joel Brobecker <brobecker@adacore.com>,
gdb@sourceware.org
Subject: Re: GDB 6.5.90 available for testing (GDB 6.6 pre-release)
Date: Tue, 05 Dec 2006 21:41:00 -0000 [thread overview]
Message-ID: <20061205214139.GA29732@nevyn.them.org> (raw)
In-Reply-To: <24560.163.1.150.229.1165354580.squirrel@webmail.xs4all.nl>
On Tue, Dec 05, 2006 at 10:36:20PM +0100, Mark Kettenis wrote:
> >
> > Here's the patch I've been using for this. It'd be better to rework
> > the way those functions use those obstacks, but...
> >
> > 2006-12-05 Jim Blandy <jimb@codesourcery.com>
> >
> > * cp-valprint.c (cp_print_value_fields, cp_print_value):
> > Initialize tmp_obstack, to avoid warnings.
> > * p-valprint.c (pascal_object_print_value_fields)
> > (pascal_object_print_value): Same.
>
> This is silly, at least if they are really unecessary. It's a bug in GCC
> and should be fixed. I mean, GCC should get better at detecting this sort
> of things; not give more false positives.
>
> Markus, can you file a GCC bug report for this?
I'm pretty sure the GCC bug was fixed in later versions of 4.1.x
already. At least, my compiler no longer warns about it. But I have
no idea how reliable that is - I can't see any vaguely efficient way to
compute this.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-12-05 21:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-02 19:23 Joel Brobecker
2006-12-04 9:35 ` Markus Deuling
2006-12-04 18:22 ` Joel Brobecker
2006-12-04 18:23 ` Daniel Jacobowitz
2006-12-05 7:02 ` Markus Deuling
2006-12-05 19:02 ` Joel Brobecker
2006-12-05 19:12 ` Jim Blandy
2006-12-05 20:09 ` Daniel Jacobowitz
2006-12-05 21:56 ` Jim Blandy
2006-12-05 20:35 ` H. J. Lu
2006-12-05 21:37 ` Mark Kettenis
2006-12-05 21:41 ` Daniel Jacobowitz [this message]
2006-12-06 16:06 ` Markus Deuling
2006-12-13 11:47 ` Markus Deuling
2006-12-04 12:09 ` Marc Kleine-Budde
2006-12-04 18:29 ` Joel Brobecker
2006-12-04 19:38 ` Ulrich Weigand
2006-12-05 7:40 ` Markus Deuling
2006-12-05 18:56 ` Joel Brobecker
2006-12-06 12:02 ` Markus Deuling
2006-12-06 17:48 ` Joel Brobecker
2006-12-07 10:00 ` Markus Deuling
2006-12-04 20:37 Kaz Kylheku
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=20061205214139.GA29732@nevyn.them.org \
--to=drow@false.org \
--cc=brobecker@adacore.com \
--cc=deuling@de.ibm.com \
--cc=gdb@sourceware.org \
--cc=jimb@codesourcery.com \
--cc=mark.kettenis@xs4all.nl \
/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