From: Pedro Alves <palves@redhat.com>
To: gdb-patches@sourceware.org
Subject: [pushed 0/2] Fix test-cp-name-parser build
Date: Tue, 12 Mar 2019 17:03:00 -0000 [thread overview]
Message-ID: <20190312170327.14109-1-palves@redhat.com> (raw)
This mini series fixes the test-cp-name-parser build.
I'm pondering what could we do to avoid these kinds of regressions.
We could make the buildbot always build these utilities too. Maybe
even better, add some testsuite testcase that smoke-tests
test-cp-name-parser.
Pedro Alves (2):
Fix test-cp-name-parser build, unused variable
Fix test-cp-name-parser build, parser_fprintf undefined
gdb/ChangeLog | 8 ++++++++
gdb/cp-name-parser.y | 1 -
gdb/yy-remap.h | 4 +++-
3 files changed, 11 insertions(+), 2 deletions(-)
--
2.14.4
next reply other threads:[~2019-03-12 17:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-12 17:03 Pedro Alves [this message]
2019-03-12 17:03 ` [pushed 2/2] Fix test-cp-name-parser build, parser_fprintf undefined Pedro Alves
2019-03-12 17:03 ` [pushed 1/2] Fix test-cp-name-parser build, unused variable Pedro Alves
2019-03-12 17:10 ` [pushed 0/2] Fix test-cp-name-parser build Tom Tromey
2019-03-12 17:23 ` Pedro Alves
2019-03-12 17:48 ` Tom Tromey
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=20190312170327.14109-1-palves@redhat.com \
--to=palves@redhat.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