Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Yao Qi <yao@codesourcery.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: New ARI warning Fri Oct 18 01:51:13 UTC 2013 in -D 2013.10.18.00.00.15
Date: Fri, 18 Oct 2013 10:15:00 -0000	[thread overview]
Message-ID: <8761sunauo.fsf@igel.home> (raw)
In-Reply-To: <52609835.4000504@codesourcery.com> (Yao Qi's message of "Fri, 18	Oct 2013 10:08:53 +0800")

Yao Qi <yao@codesourcery.com> writes:

> On 10/18/2013 09:51 AM, GDB Administrator wrote:
>> 47a48
>>> >gdb/c-varobj.c:534: code: OP eol: Do not use &&, or || at the end of a line
>> gdb/c-varobj.c:534:      if (((TYPE_CODE (type)) == TYPE_CODE_STRUCT) ||
>> 854d854
>> < gdb/varobj.c:3494: code: OP eol: Do not use &&, or || at the end of a line
>> gdb/varobj.c:3494:      if (((TYPE_CODE (type)) == TYPE_CODE_STRUCT) ||
>
> Fixed by this patch.

There are also a lot of redundant parens.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."


      reply	other threads:[~2013-10-18 10:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-18  1:51 GDB Administrator
2013-10-18  2:10 ` Yao Qi
2013-10-18 10:15   ` Andreas Schwab [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=8761sunauo.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=gdb-patches@sourceware.org \
    --cc=yao@codesourcery.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