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] Change ARI to mention C++11, and remove some rules Date: Sun, 21 Jul 2019 10:51:00 -0000 [thread overview] Message-ID: <56f79b630766bb134400b4a8da43941cfc31c0c0@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 56f79b630766bb134400b4a8da43941cfc31c0c0 *** commit 56f79b630766bb134400b4a8da43941cfc31c0c0 Author: Tom Tromey <tromey@adacore.com> AuthorDate: Mon Jul 15 10:41:18 2019 -0600 Commit: Tom Tromey <tromey@adacore.com> CommitDate: Fri Jul 19 09:37:00 2019 -0600 Change ARI to mention C++11, and remove some rules I noticed that ARI mentions "ISO C 90", but now gdb uses C++11. This patch updates some text to reflect this change. I also noticed that a few rules can be removed now. ARGSUSED doesn't seem to be an issue any more (there's no code mentioning this and I doubt most of us even remember this convention); PARAMS was specific to K&R C; and __func__ is available in C++11. gdb/ChangeLog 2019-07-19 Tom Tromey <tromey@adacore.com> * contrib/ari/gdb_ari.sh: Mention C++11, not ISO C 90. (ARGSUSED, PARAMS, __func__): Remove rules. diff --git a/gdb/ChangeLog b/gdb/ChangeLog index 2f73f30741..c5a102f315 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,3 +1,8 @@ +2019-07-19 Tom Tromey <tromey@adacore.com> + + * contrib/ari/gdb_ari.sh: Mention C++11, not ISO C 90. + (ARGSUSED, PARAMS, __func__): Remove rules. + 2019-07-19 Alan Hayward <alan.hayward@arm.com> * arm-tdep.c (_initialize_arm_tdep): Remove xml tests. diff --git a/gdb/contrib/ari/gdb_ari.sh b/gdb/contrib/ari/gdb_ari.sh index 895654150b..4bd434c8fe 100755 --- a/gdb/contrib/ari/gdb_ari.sh +++ b/gdb/contrib/ari/gdb_ari.sh @@ -27,7 +27,7 @@ LC_ALL=C ; export LC_ALL # Permanent checks take the form: -# Do not use XXXX, ISO C 90 implies YYYY +# Do not use XXXX, C++11 implies YYYY # Do not use XXXX, instead use YYYY''. # and should never be removed. @@ -255,17 +255,6 @@ BEGIN { } -# Things in comments - -BEGIN { doc["ARGSUSED"] = "\ -Do not use ARGSUSED, unnecessary" - category["ARGSUSED"] = ari_regression -} -/(^|[^_[:alnum:]])ARGSUSED([^_[:alnum:]]|$)/ { - fail("ARGSUSED") -} - - # SNIP - Strip out comments - SNIP FNR == 1 { @@ -433,27 +422,8 @@ FNR == 1 { cont_p { $0 = full_line $0; cont_p = 0; full_line = ""; } -# GDB uses ISO C 90. Check for any non pure ISO C 90 code - -BEGIN { doc["PARAMS"] = "\ -Do not use PARAMS(), ISO C 90 implies prototypes" - category["PARAMS"] = ari_regression -} -/(^|[^_[:alnum:]])PARAMS([^_[:alnum:]]|$)/ { - fail("PARAMS") -} - -BEGIN { doc["__func__"] = "\ -Do not use __func__, ISO C 90 does not support this macro" - category["__func__"] = ari_regression - fix("__func__", "gdbsupport/gdb_assert.h", 1) -} -/(^|[^_[:alnum:]])__func__([^_[:alnum:]]|$)/ { - fail("__func__") -} - BEGIN { doc["__FUNCTION__"] = "\ -Do not use __FUNCTION__, ISO C 90 does not support this macro" +Do not use __FUNCTION__, C++11 does not support this macro" category["__FUNCTION__"] = ari_regression } /(^|[^_[:alnum:]])__FUNCTION__([^_[:alnum:]]|$)/ { @@ -470,7 +440,7 @@ autoconf tests" } BEGIN { doc["PTR"] = "\ -Do not use PTR, ISO C 90 implies `void *'\''" +Do not use PTR, C++11 implies `void *'\''" category["PTR"] = ari_regression #fix("PTR", "gdb/utils.c", 6) } @@ -816,7 +786,7 @@ unconditionally" } BEGIN { doc["bcmp"] = "\ -Do not use bcmp(), ISO C 90 implies memcmp()" +Do not use bcmp(), C++11 implies memcmp()" category["bcmp"] = ari_regression } /(^|[^_[:alnum:]])bcmp[[:space:]]*\(/ { @@ -824,7 +794,7 @@ Do not use bcmp(), ISO C 90 implies memcmp()" } BEGIN { doc["setlinebuf"] = "\ -Do not use setlinebuf(), ISO C 90 implies setvbuf()" +Do not use setlinebuf(), C++11 implies setvbuf()" category["setlinebuf"] = ari_regression } /(^|[^_[:alnum:]])setlinebuf[[:space:]]*\(/ { @@ -832,7 +802,7 @@ Do not use setlinebuf(), ISO C 90 implies setvbuf()" } BEGIN { doc["bcopy"] = "\ -Do not use bcopy(), ISO C 90 implies memcpy() and memmove()" +Do not use bcopy(), C++11 implies memcpy() and memmove()" category["bcopy"] = ari_regression } /(^|[^_[:alnum:]])bcopy[[:space:]]*\(/ {
next reply other threads:[~2019-07-21 10:29 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-07-21 10:51 gdb-buildbot [this message] 2019-07-21 10:38 ` Failures on Fedora-i686, branch master gdb-buildbot 2019-07-21 10:54 ` Failures on Fedora-x86_64-m32, " gdb-buildbot 2019-07-21 11:06 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-cc-with-index, branch master *** BREAKAGE *** gdb-buildbot 2019-07-21 11:31 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, branch master gdb-buildbot 2019-07-21 11:31 ` Failures on Fedora-x86_64-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=56f79b630766bb134400b4a8da43941cfc31c0c0@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: linkBe 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).