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] Redefine gdb_static_assert as static_assert
Date: Tue, 05 Dec 2017 22:06:00 -0000	[thread overview]
Message-ID: <ed9376bd95c52ba00aa37b224b4407030a00d184@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT ed9376bd95c52ba00aa37b224b4407030a00d184 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: ed9376bd95c52ba00aa37b224b4407030a00d184

Redefine gdb_static_assert as static_assert

Since we use C++11, we can use static_assert instead doing the trick
that makes a negative-sized array if the expression is false.
static_assert is built in the language and gives clearer error messages.

To avoid modifying the usages of gdb_static_assert, redefine
gdb_static_assert in terms of static_assert, passing an empty message.
If we want to add an assert with a message, it's always possible to use
static_assert directly.

gdb/ChangeLog:

	* common/gdb_assert.h (gdb_static_assert): Redefine using
	static_assert.


             reply	other threads:[~2017-12-05 22:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-05 22:06 sergiodj+buildbot [this message]
2017-12-05 22:06 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2017-12-05 22:12 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2017-12-05 22:13 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2017-12-05 22:15 ` Failures on Fedora-i686, " sergiodj+buildbot
2017-12-05 22:26 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2017-12-05 22:36 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2017-12-05 22:53 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2017-12-05 23:17 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot
2017-12-05 23:18 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
2017-12-05 23:43 ` Failures on Ubuntu-AArch32-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=ed9376bd95c52ba00aa37b224b4407030a00d184@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).