From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sourceware.org, hongjiu.lu@intel.com
Subject: Re: PATCH: Initialize tmp_obstack
Date: Sun, 21 Jan 2007 15:59:00 -0000 [thread overview]
Message-ID: <20070121155940.GA9459@nevyn.them.org> (raw)
In-Reply-To: <200701211307.l0LD7EO0000187@brahms.sibelius.xs4all.nl>
On Sun, Jan 21, 2007 at 02:07:14PM +0100, Mark Kettenis wrote:
> I had another look and come up with the attached. By always
> initializing tmp_obstack the code is less optimal, but at least I can
> convince myself the code is safe now. Unfortunately I can't test
> whether this fixes the GCC 4.1 warnings.
Thanks! I can test it - I'll let you know this afternoon.
p-valprint.c has the same problem, but the correct fix there is going
to be to delete some code. Pascal copied a lot from C/C++ but it
doesn't actually have static members to the best of my knowledge.
I see some discussion of them as planned for GNU Pascal, but no
implementations.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-01-21 15:59 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
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 [this message]
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=20070121155940.GA9459@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=hongjiu.lu@intel.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