From: Pedro Alves <pedro@palves.net>
To: Andrew Burgess <andrew.burgess@embecosm.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdbsupport: remove attempt to define TARGET_WORD_SIZE
Date: Fri, 24 Sep 2021 17:54:53 +0100 [thread overview]
Message-ID: <9bd5f5ea-aa2a-8829-cde0-d5697dab87c1@palves.net> (raw)
In-Reply-To: <20210924164413.3770845-1-andrew.burgess@embecosm.com>
On 2021-09-24 5:44 p.m., Andrew Burgess wrote:
> In the gdbsupport configure.ac file, there is an attempt to define
> TARGET_WORD_SIZE. This is done by running grep on the file
> ../bfd/bfd-in3.h.
>
> The problem with this is, the file bfd-in3.h is generated into the bfd
> build directory when bfd is configured, and there is no dependency
> between the gdbsupport module and the bfd module, so, for example, if
> I do:
>
> $ ../src/configure
> $ make all-gdbsupport
>
> Then bfd will neither be configured, or built. In this case
> TARGET_WORD_SIZE ends up being defined, but with no value because the
> grep on bfd-in3.h fails.
>
> However, it turns out that this doesn't matter; we don't actually use
> TARGET_WORD_SIZE anywhere.
>
> My proposal in this commit is to just remove the definition of
> TARGET_WORD_SIZE, the alternative would be to add a dependency between
> configure-gdbsupport and configure-bfd into Makefile.def, but adding a
> dependency for something we don't need seems pretty pointless.
Strange, that TARGET_WORD_SIZE bits was added by 01027315f540, and AFAICS, git
grep on 01027315f540^ only finds ChangeLog hits. But it wasn't used anywhere when it
was added by commit 01027315f540 either.
Maybe Tromey remembers.
The patch LGTM.
next prev parent reply other threads:[~2021-09-24 16:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-24 16:44 Andrew Burgess
2021-09-24 16:54 ` Pedro Alves [this message]
2021-09-30 17:38 ` Tom Tromey
2021-10-04 10:24 ` Andrew Burgess
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=9bd5f5ea-aa2a-8829-cde0-d5697dab87c1@palves.net \
--to=pedro@palves.net \
--cc=andrew.burgess@embecosm.com \
--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