Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Sami Wagiaalla <swagiaal@redhat.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 1/2] namespace support
Date: Fri, 19 Jun 2009 21:33:00 -0000	[thread overview]
Message-ID: <m33a9vsybo.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4A3BEA01.20106@redhat.com> (Sami Wagiaalla's message of "Fri\, 19 Jun 2009 15\:41\:53 -0400")

>>>>> "Sami" == Sami Wagiaalla <swagiaal@redhat.com> writes:

Tom> Eww, buildsym is full of globals.  Not your problem :-), but yet
Tom> another thing that would be nice to clean up.

Sami> There is a nice clean up for this suggested by Jan. That is using the
Sami> variables in the current context object and automating saving/and
Sami> restoration of that. I'll post a patch if I get to it.

FWIW I would prefer a fuller cleanup.  This approach makes it sound
like there would still be one global -- but I don't see why we need
any globals at all.  At least, we don't need them in the dwarf reader;
I don't care as much whether the other readers have module-private
globals if that makes the change simpler.

Sami> This is a gcc bug. I filed it here:
Sami> https://bugzilla.redhat.com/show_bug.cgi?id=506524 and improved
Sami> the comment.  and improved the comment.

For future reference, it is better to file gcc bugs in the gcc
bugzilla.  They are more likely to be seen there.

Also, for some reason in your messages, the patch shows up twice.
Does anybody else see that?

The version of this patch with the new test case is ok.
Thanks.

Tom


  parent reply	other threads:[~2009-06-19 21:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-22 14:48 Sami Wagiaalla
2009-06-02 15:13 ` Sami Wagiaalla
2009-06-05  0:27 ` Tom Tromey
2009-06-19 19:43   ` Sami Wagiaalla
2009-06-19 20:15     ` Sami Wagiaalla
2009-06-19 21:33     ` Tom Tromey [this message]
2009-06-19 21:44       ` Tom Tromey

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=m33a9vsybo.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=swagiaal@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