qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Brian Cain <quic_bcain@quicinc.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>, qemu-devel@nongnu.org
Cc: "Brian Cain" <bcain@quicinc.com>,
	qemu-trivial@nongnu.org, "Anton Johansson" <anjo@rev.ng>,
	"Alessandro Di Federico" <ale@rev.ng>,
	"Daniel P. Berrangé" <berrange@redhat.com>,
	"Matheus Tavares Bernardino" <quic_mathbern@quicinc.com>
Subject: Re: [PATCH 1/2] target/hexagon: Rename macros.inc -> macros.h.inc
Date: Tue, 10 Sep 2024 08:53:37 -0500	[thread overview]
Message-ID: <83bbc1d7-350f-4fc9-812a-847f63d3a00f@quicinc.com> (raw)
In-Reply-To: <20240910112833.27594-2-philmd@linaro.org>


On 9/10/2024 6:28 AM, Philippe Mathieu-Daudé wrote:
> Since commits 139c1837db ("meson: rename included C source files
> to .c.inc") and 0979ed017f ("meson: rename .inc.h files to .h.inc"),
> EMU standard procedure for included header files is to use *.h.inc.
>
> Besides, since commit 6a0057aa22 ("docs/devel: make a statement
> about includes") this is documented in the Coding Style:
>
>    If you do use template header files they should be named with
>    the ``.c.inc`` or ``.h.inc`` suffix to make it clear they are
>    being included for expansion.
>
> Therefore rename "macros.inc" as "macros.h.inc".
>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> ---

Reviewed-by: Brian Cain <bcain@quicinc.com>


>   target/hexagon/idef-parser/README.rst                   | 4 ++--
>   target/hexagon/idef-parser/{macros.inc => macros.h.inc} | 0
>   target/hexagon/gen_idef_parser_funcs.py                 | 2 +-
>   target/hexagon/meson.build                              | 2 +-
>   4 files changed, 4 insertions(+), 4 deletions(-)
>   rename target/hexagon/idef-parser/{macros.inc => macros.h.inc} (100%)
>
> diff --git a/target/hexagon/idef-parser/README.rst b/target/hexagon/idef-parser/README.rst
> index d0aa34309b..7199177ee3 100644
> --- a/target/hexagon/idef-parser/README.rst
> +++ b/target/hexagon/idef-parser/README.rst
> @@ -138,7 +138,7 @@ we obtain the pseudo code
>   with macros such as ``fJUMPR`` intact.
>   
>   The second step is to expand macros into a form suitable for our parser.
> -These macros are defined in ``idef-parser/macros.inc`` and the step is
> +These macros are defined in ``idef-parser/macros.h.inc`` and the step is
>   carried out by the ``prepare`` script which runs the C preprocessor on
>   ``idef_parser_input.h.inc`` to produce
>   ``idef_parser_input.preprocessed.h.inc``.
> @@ -266,7 +266,7 @@ in plain C is defined as
>       #define fABS(A) (((A) < 0) ? (-(A)) : (A))
>   
>   and returns the absolute value of the argument ``A``. This macro is not included
> -in ``idef-parser/macros.inc`` and as such is not expanded and kept as a "call"
> +in ``idef-parser/macros.h.inc`` and as such is not expanded and kept as a "call"
>   ``fABS(...)``. Reason being, that ``fABS`` is easier to match and map to
>   ``tcg_gen_abs_<width>``, compared to the full ternary expression above. Loads of
>   macros in ``macros.h`` are kept unexpanded to aid in parsing, as seen in the
> diff --git a/target/hexagon/idef-parser/macros.inc b/target/hexagon/idef-parser/macros.h.inc
> similarity index 100%
> rename from target/hexagon/idef-parser/macros.inc
> rename to target/hexagon/idef-parser/macros.h.inc
> diff --git a/target/hexagon/gen_idef_parser_funcs.py b/target/hexagon/gen_idef_parser_funcs.py
> index eb494abba8..72f11c68ca 100644
> --- a/target/hexagon/gen_idef_parser_funcs.py
> +++ b/target/hexagon/gen_idef_parser_funcs.py
> @@ -50,7 +50,7 @@ def main():
>       tagimms = hex_common.get_tagimms()
>   
>       with open(sys.argv[-1], "w") as f:
> -        f.write('#include "macros.inc"\n\n')
> +        f.write('#include "macros.h.inc"\n\n')
>   
>           for tag in hex_common.tags:
>               ## Skip the priv instructions
> diff --git a/target/hexagon/meson.build b/target/hexagon/meson.build
> index 9ea1f4fc59..f1723778a6 100644
> --- a/target/hexagon/meson.build
> +++ b/target/hexagon/meson.build
> @@ -284,7 +284,7 @@ if idef_parser_enabled and 'hexagon-linux-user' in target_dirs
>           'idef_parser_input.preprocessed.h.inc',
>           output: 'idef_parser_input.preprocessed.h.inc',
>           input: idef_parser_input_generated,
> -        depend_files: [idef_parser_dir / 'macros.inc'],
> +        depend_files: [idef_parser_dir / 'macros.h.inc'],
>           command: [idef_parser_dir / 'prepare', '@INPUT@', '-I' + idef_parser_dir, '-o', '@OUTPUT@'],
>       )
>   


  reply	other threads:[~2024-09-10 13:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-10 11:28 [PATCH 0/2] misc: Rename included template headers using '.inc' suffix Philippe Mathieu-Daudé
2024-09-10 11:28 ` [PATCH 1/2] target/hexagon: Rename macros.inc -> macros.h.inc Philippe Mathieu-Daudé
2024-09-10 13:53   ` Brian Cain [this message]
2024-09-10 14:21   ` Anton Johansson via
2024-09-10 11:28 ` [PATCH 2/2] tests/bench: Rename test_akcipher_keys.inc -> test_akcipher_keys.c.inc Philippe Mathieu-Daudé
2024-09-10 19:18 ` [PATCH 0/2] misc: Rename included template headers using '.inc' suffix Richard Henderson
2024-09-20  7:09 ` Michael Tokarev

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=83bbc1d7-350f-4fc9-812a-847f63d3a00f@quicinc.com \
    --to=quic_bcain@quicinc.com \
    --cc=ale@rev.ng \
    --cc=anjo@rev.ng \
    --cc=bcain@quicinc.com \
    --cc=berrange@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=quic_mathbern@quicinc.com \
    /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 NNTP newsgroup(s).