public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/27528] compile fail (binutils/gdb/ada-lang.c)
Date: Sat, 06 Mar 2021 16:43:04 +0000	[thread overview]
Message-ID: <bug-27528-4717-kHq6EaHsWn@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27528-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=27528

--- Comment #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom Tromey <tromey@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=01573d7360cdd9660fdc6bf48b0b7f2180f5c40c

commit 01573d7360cdd9660fdc6bf48b0b7f2180f5c40c
Author: Tom Tromey <tom@tromey.com>
Date:   Sat Mar 6 09:38:26 2021 -0700

    Fix build bug in ada-lang.c

    An earlier patch of mine introduced a build failure in ada-lang.c.  A
    couple of "to_string" calls were not namespace-qualified.  In the
    failing setup, the std string_view is being used, and so (apparently)
    ADL doesn't find gdb::to_string.

    This patch, from the bug, fixes the problem.

    gdb/ChangeLog
    2021-03-06  Chernov Sergey  <klen_s@mail.ru>

            PR gdb/27528:
            * ada-lang.c (ada_fold_name): Use gdb::to_string.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2021-03-06 16:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-05 21:48 [Bug gdb/27528] New: " klen_s at mail dot ru
2021-03-05 21:52 ` [Bug gdb/27528] " klen_s at mail dot ru
2021-03-06 16:43 ` cvs-commit at gcc dot gnu.org [this message]
2021-03-06 16:43 ` tromey at sourceware dot org

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=bug-27528-4717-kHq6EaHsWn@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /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).