public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: sergiodj+buildbot@sergiodj.net
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] Remove file and line from struct complain
Date: Wed, 23 May 2018 19:22:00 -0000 [thread overview]
Message-ID: <7ff8817441fcebe3d32343dbd9d514366bfe8e23@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 7ff8817441fcebe3d32343dbd9d514366bfe8e23 ***
Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 7ff8817441fcebe3d32343dbd9d514366bfe8e23
Remove file and line from struct complain
The file and line handling in complaints.c wasn't used once
internal_complaint was removed. This patch removes all the related
code.
gdb/ChangeLog
2018-05-23 Tom Tromey <tom@tromey.com>
* complaints.c (struct complain) <file, line>: Remove.
(find_complaint): Remove file, line parameters.
(complaint_internal): Update.
next reply other threads:[~2018-05-23 19:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-23 19:22 sergiodj+buildbot [this message]
2018-05-23 19:41 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-23 19:41 ` Failures on RHEL-s390x-m64, " sergiodj+buildbot
2018-05-24 22:03 ` Failures on Debian-s390x-m64, " sergiodj+buildbot
2018-05-24 23:10 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2018-06-01 23:04 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2018-06-01 23:49 ` Failures on Fedora-i686, " sergiodj+buildbot
2018-06-02 0:13 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-w64-mingw32, branch master *** BREAKAGE *** sergiodj+buildbot
2018-08-24 3:01 ` Failures on Ubuntu-AArch32-m32, branch master sergiodj+buildbot
2018-08-24 6:59 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
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=7ff8817441fcebe3d32343dbd9d514366bfe8e23@gdb-build \
--to=sergiodj+buildbot@sergiodj.net \
--cc=gdb-testers@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).