qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: "Eric Blake" <eblake@redhat.com>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	"Peter Maydell" <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] Hacks for building on gcc 7 / Fedora 26
Date: Wed, 19 Jul 2017 09:15:29 +0200	[thread overview]
Message-ID: <5c29a13f-6a0d-6074-1ac4-e4491a2a0cdc@redhat.com> (raw)
In-Reply-To: <2a198132-689f-9cf2-42da-3b481e49af3a@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 938 bytes --]

On 18.07.2017 17:10, Eric Blake wrote:
> On 07/18/2017 10:04 AM, Philippe Mathieu-Daudé wrote:
>>> We should be consistent -- if we can't trust assert() to
>>> be marked nonreturn, as it seems we can't, then we shouldn't
>>> write new code that assumes it always is, even if today
>>> it doesn't happen to bite us on the compiler/host combinations
>>> we're testing right now.
>>
>> And there is also the problem when you compiles with CPPFLAGS+=-DNDEBUG
>> some oldschool guys still have in their ~/.cshrc ;)
> 
> We don't have problems with people defining NDEBUG in their environment;
> such people would already hit at least:
> 
> hw/scsi/mptsas.c:#ifdef NDEBUG
> hw/scsi/mptsas.c:#error building with NDEBUG is not supported
> 
> (maybe we should hoist that to osdep.h, though)

Yes, please. Not every target is build with CONFIG_MPTSAS_SCSI_PCI so we
should move that to a more central place.

 Thomas




[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2017-07-19  7:15 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-07 14:38 [Qemu-devel] Hacks for building on gcc 7 / Fedora 26 Dr. David Alan Gilbert
2017-04-07 19:21 ` Philippe Mathieu-Daudé
2017-07-13 13:07   ` Philippe Mathieu-Daudé
2017-07-17 13:42     ` Eric Blake
2017-07-17 13:48       ` Eric Blake
2017-07-17 14:16         ` Gerd Hoffmann
2017-07-17 15:04           ` Eric Blake
2017-07-17 16:46         ` Dr. David Alan Gilbert
2017-07-17 17:22           ` Peter Maydell
2017-07-17 17:29           ` Eric Blake
2017-07-17 17:36             ` Peter Maydell
2017-07-17 18:10               ` Eric Blake
2017-07-17 18:48                 ` Dr. David Alan Gilbert
2017-07-18 15:04               ` Philippe Mathieu-Daudé
2017-07-18 15:10                 ` Eric Blake
2017-07-19  7:15                   ` Thomas Huth [this message]
2017-07-17 17:46             ` Dr. David Alan Gilbert
2017-07-18  7:23             ` Daniel P. Berrange
2017-07-18 12:35               ` Eric Blake
2017-07-18 12:56                 ` Daniel P. Berrange
2017-07-18 23:59         ` Richard Henderson
2017-07-19  0:34           ` Eric Blake
2017-04-12 23:54 ` no-reply
2017-07-20 10:50 ` Daniel P. Berrange
2017-07-20 12:10   ` Eric Blake
2017-07-20 16:15   ` Dr. David Alan Gilbert
2017-07-20 16:47     ` Daniel P. Berrange
2017-07-20 17:04       ` Dr. David Alan Gilbert
2017-07-20 17:06         ` Daniel P. Berrange
2017-07-20 18:36           ` Eric Blake

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=5c29a13f-6a0d-6074-1ac4-e4491a2a0cdc@redhat.com \
    --to=thuth@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=eblake@redhat.com \
    --cc=f4bug@amsat.org \
    --cc=kraxel@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.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 NNTP newsgroup(s).