public inbox for archer@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: archer@sourceware.org
Subject: Re: [expr-cumulative] Fix namespace regression for G++-4.1
Date: Mon, 21 Dec 2009 18:32:00 -0000	[thread overview]
Message-ID: <m3aaxcb2kg.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20091220113428.GA11119@host0.dyn.jankratochvil.net> (Jan Kratochvil's message of "Sun, 20 Dec 2009 12:34:28 +0100")

>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:

Jan> but the code is not present in current
Jan> archer-keiths-expr-cumulative and thus this branch regresses on the
Jan> testcase against FSF GDB.

Jan> On G++-4.1 code it creates GDB symbol "::::var".

Jan> OK to check it in archer-keiths-expr-cumulative?

It looks reasonable to me.

Go ahead and check it in, and if Keith doesn't like it, we can deal with
it when he is back from the holidays.

Tom

  reply	other threads:[~2009-12-21 18:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-20 11:34 Jan Kratochvil
2009-12-21 18:32 ` Tom Tromey [this message]
2009-12-23 21:35   ` Jan Kratochvil

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=m3aaxcb2kg.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=archer@sourceware.org \
    --cc=jan.kratochvil@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).