public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: gdb-buildbot@sergiodj.net
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] Remove "fix" call for "long long" from ARI
Date: Mon, 16 Dec 2019 11:39:00 -0000 [thread overview]
Message-ID: <93537683e79f8a55c51ffa00008966e32ee8e4a7@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 93537683e79f8a55c51ffa00008966e32ee8e4a7 ***
commit 93537683e79f8a55c51ffa00008966e32ee8e4a7
Author: Tom Tromey <tromey@adacore.com>
AuthorDate: Thu Dec 12 09:10:49 2019 -0700
Commit: Tom Tromey <tromey@adacore.com>
CommitDate: Fri Dec 13 15:15:32 2019 -0700
Remove "fix" call for "long long" from ARI
ARI has a "fix" call for "long long", but this call is incorrect.
This patch removes it.
gdb/ChangeLog
2019-12-13 Tom Tromey <tromey@adacore.com>
* contrib/ari/gdb_ari.sh: Remove call to "fix" for "long long".
Change-Id: I97bca2dc04b579fcf7c9dba7fe7fd939451bcefa
diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index d30611fa26..90c3742e93 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,7 @@
+2019-12-13 Tom Tromey <tromey@adacore.com>
+
+ * contrib/ari/gdb_ari.sh: Remove call to "fix" for "long long".
+
2019-12-13 Tom Tromey <tromey@adacore.com>
* contrib/ari/gdb_ari.sh: Handle -Wno- prefix.
diff --git a/gdb/contrib/ari/gdb_ari.sh b/gdb/contrib/ari/gdb_ari.sh
index 02c3647388..5f058906d0 100755
--- a/gdb/contrib/ari/gdb_ari.sh
+++ b/gdb/contrib/ari/gdb_ari.sh
@@ -587,8 +587,6 @@ Do not use strerror(), instead use safe_strerror()"
BEGIN { doc["long long"] = "\
Do not use `long long'\'', instead use LONGEST"
category["long long"] = ari_code
- # defs.h needs two such patterns for LONGEST and ULONGEST definitions
- fix("long long", "gdb/defs.h", 2)
}
/(^|[^_[:alnum:]])long[[:space:]]+long([^_[:alnum:]]|$)/ {
fail("long long")
next reply other threads:[~2019-12-16 11:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 11:39 gdb-buildbot [this message]
2019-12-16 11:59 ` Failures on Ubuntu-Aarch64-m64, branch master gdb-buildbot
2019-12-16 12:16 ` Failures on Ubuntu-Aarch64-native-extended-gdbserver-m64, " gdb-buildbot
2019-12-16 12:32 ` Failures on Ubuntu-Aarch64-native-gdbserver-m64, " gdb-buildbot
2019-12-17 22:04 ` Failures on Fedora-x86_64-cc-with-index, " gdb-buildbot
2019-12-17 22:18 ` Failures on Fedora-x86_64-m64, " gdb-buildbot
2019-12-17 22:34 ` Failures on Fedora-x86_64-m32, " gdb-buildbot
2019-12-17 22:39 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " gdb-buildbot
2019-12-17 23:04 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " gdb-buildbot
2019-12-17 23:14 ` Failures on Fedora-x86_64-native-gdbserver-m64, " gdb-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=93537683e79f8a55c51ffa00008966e32ee8e4a7@gdb-build \
--to=gdb-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).