public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: gdb-buildbot@sergiodj.net
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] Remove self-assign from make_invisible_and_set_new_height
Date: Mon, 22 Jul 2019 15:04:00 -0000	[thread overview]
Message-ID: <bfa2a36d94d124eb7b54fd271a543047579b47ee@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT bfa2a36d94d124eb7b54fd271a543047579b47ee ***

commit bfa2a36d94d124eb7b54fd271a543047579b47ee
Author:     Tom Tromey <tom@tromey.com>
AuthorDate: Mon Jul 22 08:34:25 2019 -0600
Commit:     Tom Tromey <tom@tromey.com>
CommitDate: Mon Jul 22 08:34:25 2019 -0600

    Remove self-assign from make_invisible_and_set_new_height
    
    In https://sourceware.org/ml/gdb-patches/2019-07/msg00509.html, Jan
    pointed out that clang points out that
    make_invisible_and_set_new_height self-assigns "height".
    
    This patch fixes the bug by renaming the formal parameter.
    
    gdb/ChangeLog
    2019-07-22  Tom Tromey  <tom@tromey.com>
    
            * tui/tui-win.c (tui_win_info::make_invisible_and_set_new_height):
            Don't self-assign.

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 63d6712432..bf12f0ef41 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,8 @@
+2019-07-22  Tom Tromey  <tom@tromey.com>
+
+	* tui/tui-win.c (tui_win_info::make_invisible_and_set_new_height):
+	Don't self-assign.
+
 2019-07-22  Andrew Burgess  <andrew.burgess@embecosm.com>
 
 	* c-typeprint.c (c_print_typedef): Pass -1 instead of 0 to
diff --git a/gdb/tui/tui-win.c b/gdb/tui/tui-win.c
index db4dc1088a..785c623b7e 100644
--- a/gdb/tui/tui-win.c
+++ b/gdb/tui/tui-win.c
@@ -1194,10 +1194,10 @@ tui_adjust_win_heights (struct tui_win_info *primary_win_info,
 /* See tui-data.h.  */
 
 void
-tui_win_info::make_invisible_and_set_new_height (int height)
+tui_win_info::make_invisible_and_set_new_height (int height_)
 {
   make_visible (false);
-  height = height;
+  height = height_;
   if (height > 1)
     viewport_height = height - 1;
   else


             reply	other threads:[~2019-07-22 15:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-22 15:04 gdb-buildbot [this message]
2019-07-22 15:20 ` Failures on Fedora-i686, branch master gdb-buildbot
2019-07-22 15:27 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " gdb-buildbot
2019-07-22 15:34 ` Failures on Fedora-x86_64-cc-with-index, " gdb-buildbot
2019-07-22 15:58 ` Failures on Fedora-x86_64-m32, " gdb-buildbot
2019-07-22 16:56 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " gdb-buildbot
2019-07-23  9:03 ` Failures on Fedora-x86_64-native-gdbserver-m32, " gdb-buildbot
2019-07-23  9:03 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-native-gdbserver-m64, branch master *** BREAKAGE *** gdb-buildbot

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=bfa2a36d94d124eb7b54fd271a543047579b47ee@gdb-build \
    --to=gdb-buildbot@sergiodj.net \
    --cc=gdb-testers@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).