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 unused includes in aarch64-linux-tdep.c
Date: Wed, 04 Dec 2019 23:40:00 -0000	[thread overview]
Message-ID: <be155ebb949dd8e7ef6a494a9c276c3c4673643c@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT be155ebb949dd8e7ef6a494a9c276c3c4673643c ***

commit be155ebb949dd8e7ef6a494a9c276c3c4673643c
Author:     Simon Marchi <simon.marchi@polymtl.ca>
AuthorDate: Wed Dec 4 13:33:02 2019 -0500
Commit:     Simon Marchi <simon.marchi@efficios.com>
CommitDate: Wed Dec 4 13:33:02 2019 -0500

    Remove unused includes in aarch64-linux-tdep.c
    
    include-what-you-use reports:
    
    ../../../src/binutils-gdb/gdb/aarch64-linux-tdep.c should remove these lines:
    - #include "arch-utils.h"  // lines 24-24
    - #include "auxv.h"  // lines 48-48
    - #include "cli/cli-utils.h"  // lines 39-39
    - #include "elf/common.h"  // lines 49-49
    - #include "inferior.h"  // lines 35-35
    
    Add an include for "target/target.h", otherwise target_read_memory isn't
    found.
    
    gdb/ChangeLog:
    
            * aarch64-linux-tdep.c: Remove includes.

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index f0ec1e6434..50f32638b4 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,7 @@
+2019-12-04  Simon Marchi  <simon.marchi@polymtl.ca>
+
+	* aarch64-linux-tdep.c: Remove includes.
+
 2019-12-04  Simon Marchi  <simon.marchi@polymtl.ca>
 
 	* aarch64-tdep.c: Remove includes.
diff --git a/gdb/aarch64-linux-tdep.c b/gdb/aarch64-linux-tdep.c
index c8e30a4fef..1d4aac7a87 100644
--- a/gdb/aarch64-linux-tdep.c
+++ b/gdb/aarch64-linux-tdep.c
@@ -21,7 +21,6 @@
 #include "defs.h"
 
 #include "gdbarch.h"
-#include "arch-utils.h"
 #include "glibc-tdep.h"
 #include "linux-tdep.h"
 #include "aarch64-tdep.h"
@@ -31,12 +30,11 @@
 #include "symtab.h"
 #include "tramp-frame.h"
 #include "trad-frame.h"
+#include "target/target.h"
 
-#include "inferior.h"
 #include "regcache.h"
 #include "regset.h"
 
-#include "cli/cli-utils.h"
 #include "stap-probe.h"
 #include "parser-defs.h"
 #include "user-regs.h"
@@ -45,8 +43,6 @@
 
 #include "record-full.h"
 #include "linux-record.h"
-#include "auxv.h"
-#include "elf/common.h"
 
 /* Signal frame handling.
 


             reply	other threads:[~2019-12-04 23:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-04 23:40 gdb-buildbot [this message]
2019-12-04 23:36 ` Failures on Ubuntu-Aarch64-native-extended-gdbserver-m64, branch master gdb-buildbot
2019-12-04 23:53 ` Failures on Ubuntu-Aarch64-native-gdbserver-m64, " gdb-buildbot
2019-12-05  6:02 ` Failures on Fedora-i686, " gdb-buildbot
2019-12-05  6:03 ` Failures on Fedora-x86_64-cc-with-index, " gdb-buildbot
2019-12-05  6:29 ` Failures on Fedora-x86_64-m32, " gdb-buildbot
2019-12-05  6:37 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " gdb-buildbot
2019-12-05  6:44 ` Failures on Fedora-x86_64-native-gdbserver-m32, " gdb-buildbot
2019-12-05  7:13 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " 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=be155ebb949dd8e7ef6a494a9c276c3c4673643c@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).