public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gdb-patches@sourceware.org
Subject: [PATCH] sim: drop unused CORE_ADDR_TYPE
Date: Tue,  8 Nov 2022 14:10:31 +0700	[thread overview]
Message-ID: <20221108071031.15585-1-vapier@gentoo.org> (raw)

This hasn't been used by gdb in decades, and doesn't make sense with
a standalone sim program/library where the ABI is fixed.  So punt it
to simplify the code.
---
 include/sim/sim.h | 7 -------
 1 file changed, 7 deletions(-)

diff --git a/include/sim/sim.h b/include/sim/sim.h
index 5569481da991..20a667cab7d3 100644
--- a/include/sim/sim.h
+++ b/include/sim/sim.h
@@ -27,14 +27,7 @@ extern "C" {
 /* This file is used when building stand-alone simulators, so isolate this
    file from gdb.  */
 
-/* Pick up CORE_ADDR_TYPE if defined (from gdb), otherwise use same value as
-   gdb does (unsigned int - from defs.h).  */
-
-#ifndef CORE_ADDR_TYPE
 typedef unsigned int SIM_ADDR;
-#else
-typedef CORE_ADDR_TYPE SIM_ADDR;
-#endif
 
 
 /* Semi-opaque type used as result of sim_open and passed back to all
-- 
2.38.1


                 reply	other threads:[~2022-11-08  7:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20221108071031.15585-1-vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).