Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: Re: New ARI warning Wed Dec 18 01:52:57 UTC 2013
Date: Wed, 18 Dec 2013 02:47:00 -0000	[thread overview]
Message-ID: <20131218024740.GB3493@adacore.com> (raw)
In-Reply-To: <20131218015257.GA31623@sourceware.org>

[-- Attachment #1: Type: text/plain, Size: 420 bytes --]

> 834a835
> > gdb/value.c:383: code: OP eol: Do not use &&, or || at the end of a line
> gdb/value.c:383:	  && t->length == (TARGET_CHAR_BIT *

This was looked easy to fix, so I just went ahead and did it:

gdb/ChangeLog:

        * value.c (value_entirely_unavailable): ARI fix: Move trailing
        binary operator to the next line.  No actual code change.

Tested on x86_64-linux by simply rebuilding GDB.

-- 
Joel

[-- Attachment #2: 0001-ARI-fix-in-value.c-value_entirely_unavailable.patch --]
[-- Type: text/x-diff, Size: 1374 bytes --]

From 64c46ce4ace879a65e62933afac2f540ffbc40aa Mon Sep 17 00:00:00 2001
From: Joel Brobecker <brobecker@adacore.com>
Date: Wed, 18 Dec 2013 06:42:49 +0400
Subject: [PATCH] ARI fix in value.c::value_entirely_unavailable

gdb/ChangeLog:

        * value.c (value_entirely_unavailable): ARI fix: Move trailing
        binary operator to the next line.  No actual code change.
---
 gdb/ChangeLog | 5 +++++
 gdb/value.c   | 4 ++--
 2 files changed, 7 insertions(+), 2 deletions(-)

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 71cf9c6..e9cb6ca 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,8 @@
+2013-12-18  Joel Brobecker  <brobecker@adacore.com>
+
+	* value.c (value_entirely_unavailable): ARI fix: Move trailing
+	binary operator to the next line.  No actual code change.
+
 2013-12-17  Pedro Alves  <palves@redhat.com>
 
 	* frame.h (enum frame_id_stack_status): New enum.
diff --git a/gdb/value.c b/gdb/value.c
index 66adaca..25c9f32 100644
--- a/gdb/value.c
+++ b/gdb/value.c
@@ -380,8 +380,8 @@ value_entirely_unavailable (struct value *value)
       struct range *t = VEC_index (range_s, value->unavailable, 0);
 
       if (t->offset == 0
-	  && t->length == (TARGET_CHAR_BIT *
-			   TYPE_LENGTH (value_enclosing_type (value))))
+	  && t->length == (TARGET_CHAR_BIT
+			   * TYPE_LENGTH (value_enclosing_type (value))))
 	return 1;
     }
 
-- 
1.8.1.2


      reply	other threads:[~2013-12-18  2:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-18  1:53 GDB Administrator
2013-12-18  2:47 ` Joel Brobecker [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=20131218024740.GB3493@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@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