From: Joel Brobecker <brobecker@adacore.com>
To: Simon Marchi <simark@simark.ca>
Cc: gdb-patches@sourceware.org
Subject: Re: New ARI warning Fri May 18 01:56:48 UTC 2018
Date: Fri, 18 May 2018 19:29:00 -0000 [thread overview]
Message-ID: <20180518190346.4yy6e7dfn7bwascu@adacore.com> (raw)
In-Reply-To: <9f29119c84b9d58b4499929bb752be78@simark.ca>
> > You can tag them as OK with a /* ARI: ... */ comment.
> >
> > But I suspect we just want to exclude files in gdb/unittests instead?
> > Here is a patch that does that. Tested by checking the change in
> > output before and after:
> >
> > 1101,1120d1100
> > < ./unittests/array-view-selftests.c
> > < ./unittests/common-utils-selftests.c
> > < ./unittests/environ-selftests.c
> > < ./unittests/function-view-selftests.c
> > < ./unittests/lookup_name_info-selftests.c
> > < ./unittests/memory-map-selftests.c
> > < ./unittests/memrange-selftests.c
> > < ./unittests/observable-selftests.c
> > < ./unittests/offset-type-selftests.c
> > < ./unittests/optional-selftests.c
> > < ./unittests/ptid-selftests.c
> > < ./unittests/rsp-low-selftests.c
> > < ./unittests/scoped_fd-selftests.c
> > < ./unittests/scoped_mmap-selftests.c
> > < ./unittests/scoped_restore-selftests.c
> > < ./unittests/string_view-selftests.c
> > < ./unittests/tracepoint-selftests.c
> > < ./unittests/unpack-selftests.c
> > < ./unittests/utils-selftests.c
> > < ./unittests/xml-utils-selftests.c
> >
> > gdb/ChangeLog:
> >
> > * contrib/ari/gdb_find.sh: Exclude the unittest directory.
>
> I don't really mind, maybe some rules related to formatting would still be
> appropriate for unittests/.
Right, which is why I formulated this as a question. I don't really
know what style we want there. But since it was easy to patch the
script, I thought I'd send that right away, to show one of the options.
But I'd be OK with deciding that unittests/ should follow the GDB
coding standards.
> Is is possible to exclude unittests/* instead of listing all the
> files? We'll surely add new files in there, and don't want to have to
> update that script every time.
This is exactly what the patch I sent does. The above was just
the diff of output between before and after patch (sorry for
the cryptic message).
find "$@" \
-name testsuite -prune -o \
+ -name unittests -prune -o \
-name gdbserver -prune -o \
-name gdbtk -prune -o \
-name gnulib -prune -o \
--
Joel
next prev parent reply other threads:[~2018-05-18 19:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-18 2:06 GDB Administrator
2018-05-18 2:14 ` Simon Marchi
2018-05-18 18:51 ` Joel Brobecker
2018-05-18 19:00 ` Simon Marchi
2018-05-18 19:29 ` Joel Brobecker [this message]
2018-05-18 19:38 ` Simon Marchi
2018-05-18 20:05 ` 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=20180518190346.4yy6e7dfn7bwascu@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
/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