Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 3/3] Build gdb "nat" files in subdirectory
Date: Thu, 27 Dec 2018 04:29:00 -0000	[thread overview]
Message-ID: <a94ae4ba-eb79-876a-593d-0eeeb0da92a1@simark.ca> (raw)
In-Reply-To: <20181224210927.16741-4-tom@tromey.com>

On 2018-12-24 4:09 p.m., Tom Tromey wrote:
> This moves the various "nat" object files into the nat/ subdirectory.
> This allows for the removal of a pattern rule from the gdb Makefile,
> which is a small cleanup.
> 
> I made the configure.nat change in a (semi-) automated way, hopefully
> meaning that it is more likely to be correct than had I done it by
> hand.
> 
> Eventually I would like for the various configure scripts to only
> mention source files, and let the Makefile compute the object file
> names.

I wrote a small script scraping all .o file names from configure.nat, to
see if there is a corresponding .c file (see below if you need it).  The
only bad one it found is "nat/aarch64-sve-nat/linux-ptrace.o", which should
just be nat/linux-ptrace.o, I think.

Other than that, it did fine the _U/_S files for Hurd (e.g. notify_S.o).  There
is no corresponding .c file for that, I don't know if they are generated or what,
but I don't think your patch changes anything about that.

If you run the script, you'll see it also reports gnu.c... it's a false positive
because it matches "gnu.o" in http://www.gnu.org/licenses :).

Overall this series LGTM, thanks!

Simon


import os
import re

with open('configure.nat') as f:
	text = f.read()

m = re.findall(r'[a-zA-Z0-9/_-]+\.o', text)

for o in m:
	c = o[:-1] + 'c'
	if not os.path.isfile(c):
		print('Missing ' + c)



  reply	other threads:[~2018-12-27  4:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-24 21:09 [PATCH 0/3] some minor Makefile improvements Tom Tromey
2018-12-24 21:09 ` [PATCH 3/3] Build gdb "nat" files in subdirectory Tom Tromey
2018-12-27  4:29   ` Simon Marchi [this message]
2018-12-27 20:03     ` Tom Tromey
2018-12-24 21:10 ` [PATCH 1/3] Remove gdbtypes special case from init.c rule Tom Tromey
2018-12-24 21:10 ` [PATCH 2/3] Make init.c depend on source files Tom Tromey
2018-12-27  4:02   ` Simon Marchi
2018-12-27  4:21     ` Tom Tromey
2018-12-27  4:23       ` Simon Marchi
2018-12-27  4:24         ` Simon Marchi

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=a94ae4ba-eb79-876a-593d-0eeeb0da92a1@simark.ca \
    --to=simark@simark.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.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