Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: John Baldwin <jhb@freebsd.org>, gdb-patches@sourceware.org
Cc: GDB Administrator <gdbadmin@sourceware.org>
Subject: Re: New ARI warning Thu Nov 24 01:57:17 UTC 2016
Date: Thu, 24 Nov 2016 16:36:00 -0000	[thread overview]
Message-ID: <1e035f32-7c10-bbd8-85ec-56b001abfe9a@redhat.com> (raw)
In-Reply-To: <2343714.57bNQKpj40@ralph.baldwin.cx>

On 11/24/2016 02:48 AM, John Baldwin wrote:
> On Thursday, November 24, 2016 01:57:18 AM GDB Administrator wrote:
>> 679a679
>>> gdb/utils.c:1878: code: no parameter function: Function having no parameter should be declared with funcname (void).
>> gdb/utils.c:1878:get_prompt_for_continue_wait_time ()
> 
> Should this ARI check be dropped since this is normal C++?

Yes.

Thanks,
Pedro Alves


      reply	other threads:[~2016-11-24 16:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-24  1:57 GDB Administrator
2016-11-24  2:48 ` John Baldwin
2016-11-24 16:36   ` Pedro Alves [this message]

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=1e035f32-7c10-bbd8-85ec-56b001abfe9a@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=gdbadmin@sourceware.org \
    --cc=jhb@freebsd.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