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/committed 3/4] sim: common: include sim-types.h in the endian header directly
Date: Wed,  3 Jan 2024 02:19:27 -0500	[thread overview]
Message-ID: <20240103071928.26550-3-vapier@gentoo.org> (raw)
In-Reply-To: <20240103071928.26550-1-vapier@gentoo.org>

This is a bit redundant for most ports as they go through sim-basics.h
which always includes sim-types.h before including sim-endian.h, but in
order to unify ppc's sim-endian code, we need this include here.  Plus,
it's the directly we generally want to go to get away from one header
that defines all APIs and causes hard to untangle dependencies.
---
 sim/common/sim-endian.h | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/sim/common/sim-endian.h b/sim/common/sim-endian.h
index 589169ea11cf..93a6d0d8c13a 100644
--- a/sim/common/sim-endian.h
+++ b/sim/common/sim-endian.h
@@ -23,6 +23,8 @@
 #ifndef SIM_ENDIAN_H
 #define SIM_ENDIAN_H
 
+#include "sim-types.h"
+
 /* C byte conversion functions */
 
 INLINE_SIM_ENDIAN(unsigned_1) endian_h2t_1(unsigned_1 x);
-- 
2.43.0


  parent reply	other threads:[~2024-01-03  7:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-03  7:19 [PATCH/committed 1/4] sim: ppc: sync WITH_TARGET_{ADDRESS,CELL}_BITSIZE with common/ Mike Frysinger
2024-01-03  7:19 ` [PATCH/committed 2/4] sim: ppc: rename local ALU SIGNED64 macros Mike Frysinger
2024-01-03  7:19 ` Mike Frysinger [this message]
2024-01-03  7:19 ` [PATCH/committed 4/4] sim: ppc: switch to common endian code Mike Frysinger

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=20240103071928.26550-3-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).