From: Markus Armbruster <armbru@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Daniel P. Berrange" <berrange@redhat.com>,
QEMU Trivial <qemu-trivial@nongnu.org>,
Paolo Bonzini <pbonzini@redhat.com>,
"patches\@linaro.org" <patches@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH] Drop QEMU_GNUC_PREREQ() checks for gcc older than 4.1
Date: Tue, 31 Jan 2017 20:02:19 +0100 [thread overview]
Message-ID: <87bmunnjd0.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <CAFEAcA_utwK=JxC7aa9chZa2DjuGkBfGAYrEfXVo86pZ5u5-zg@mail.gmail.com> (Peter Maydell's message of "Tue, 31 Jan 2017 18:32:38 +0000")
Peter Maydell <peter.maydell@linaro.org> writes:
> On 31 January 2017 at 18:11, Daniel P. Berrange <berrange@redhat.com> wrote:
>> On Tue, Jan 31, 2017 at 06:00:13PM +0000, Peter Maydell wrote:
>>> We have attributes which we wrap in QEMU_ macros already
>>> even though they always expand to the same thing:
>>> QEMU_NORETURN and QEMU_ALIGNED. I'm happy to leave these
>>> to follow that pattern. (If you wanted to send a patch
>>> series that uninlined all of those then I wouldn't hugely
>>> object to it, but I think it touches enough files that it's
>>> a separate thing from removing the #if guards that this
>>> patch does.)
>>
>> The other option is just to replace QEMU_WARN_UNUSED_RESULT with
>>
>> #define QEMU_WARN_UNUSED_RESULT G_GNUC_WARN_UNUSED_RESULT
>>
>> and convert code to use G_GNUC_WARN_UNUSED_RESULT directly until we
>> can kill the QEMU specific define. There's no benefit to QEMU having
>> its own defines that duplicate stuff already covered by our min
>> required glib - G_GNUC_WARN_UNUSED_RESULT was added in 2.10 for
>> example.
>
> I wouldn't object to that either, but again it ought to be
> a different patch or patch series to this one...
I wouldn't exactly object, just say that to me, wrapping an attribute in
a GLib-provided macro even though we're not aware of a compiler that
profits from it feels a bit like "look ma, I've read all of the GLib
manual!"
WARNING: multiple messages have this Message-ID (diff)
From: Markus Armbruster <armbru@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Daniel P. Berrange" <berrange@redhat.com>,
QEMU Trivial <qemu-trivial@nongnu.org>,
Paolo Bonzini <pbonzini@redhat.com>,
"patches@linaro.org" <patches@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] Drop QEMU_GNUC_PREREQ() checks for gcc older than 4.1
Date: Tue, 31 Jan 2017 20:02:19 +0100 [thread overview]
Message-ID: <87bmunnjd0.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <CAFEAcA_utwK=JxC7aa9chZa2DjuGkBfGAYrEfXVo86pZ5u5-zg@mail.gmail.com> (Peter Maydell's message of "Tue, 31 Jan 2017 18:32:38 +0000")
Peter Maydell <peter.maydell@linaro.org> writes:
> On 31 January 2017 at 18:11, Daniel P. Berrange <berrange@redhat.com> wrote:
>> On Tue, Jan 31, 2017 at 06:00:13PM +0000, Peter Maydell wrote:
>>> We have attributes which we wrap in QEMU_ macros already
>>> even though they always expand to the same thing:
>>> QEMU_NORETURN and QEMU_ALIGNED. I'm happy to leave these
>>> to follow that pattern. (If you wanted to send a patch
>>> series that uninlined all of those then I wouldn't hugely
>>> object to it, but I think it touches enough files that it's
>>> a separate thing from removing the #if guards that this
>>> patch does.)
>>
>> The other option is just to replace QEMU_WARN_UNUSED_RESULT with
>>
>> #define QEMU_WARN_UNUSED_RESULT G_GNUC_WARN_UNUSED_RESULT
>>
>> and convert code to use G_GNUC_WARN_UNUSED_RESULT directly until we
>> can kill the QEMU specific define. There's no benefit to QEMU having
>> its own defines that duplicate stuff already covered by our min
>> required glib - G_GNUC_WARN_UNUSED_RESULT was added in 2.10 for
>> example.
>
> I wouldn't object to that either, but again it ought to be
> a different patch or patch series to this one...
I wouldn't exactly object, just say that to me, wrapping an attribute in
a GLib-provided macro even though we're not aware of a compiler that
profits from it feels a bit like "look ma, I've read all of the GLib
manual!"
next prev parent reply other threads:[~2017-01-31 19:02 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 16:14 [Qemu-trivial] [PATCH] Drop QEMU_GNUC_PREREQ() checks for gcc older than 4.1 Peter Maydell
2017-01-31 16:14 ` [Qemu-devel] " Peter Maydell
2017-01-31 16:55 ` [Qemu-trivial] " Daniel P. Berrange
2017-01-31 16:55 ` Daniel P. Berrange
2017-01-31 16:58 ` [Qemu-trivial] " Peter Maydell
2017-01-31 16:58 ` Peter Maydell
2017-01-31 23:27 ` [Qemu-trivial] " Paolo Bonzini
2017-01-31 23:27 ` Paolo Bonzini
2017-01-31 17:40 ` [Qemu-trivial] " Markus Armbruster
2017-01-31 17:40 ` Markus Armbruster
2017-01-31 18:00 ` [Qemu-trivial] " Peter Maydell
2017-01-31 18:00 ` Peter Maydell
2017-01-31 18:11 ` [Qemu-trivial] " Daniel P. Berrange
2017-01-31 18:11 ` Daniel P. Berrange
2017-01-31 18:32 ` [Qemu-trivial] " Peter Maydell
2017-01-31 18:32 ` Peter Maydell
2017-01-31 19:02 ` Markus Armbruster [this message]
2017-01-31 19:02 ` Markus Armbruster
2017-01-31 18:58 ` [Qemu-trivial] " Markus Armbruster
2017-01-31 18:58 ` Markus Armbruster
2017-01-31 23:27 ` [Qemu-trivial] " Paolo Bonzini
2017-01-31 23:27 ` Paolo Bonzini
2017-02-01 6:49 ` [Qemu-trivial] " Markus Armbruster
2017-02-01 6:49 ` Markus Armbruster
2017-02-02 1:09 ` [Qemu-trivial] " Paolo Bonzini
2017-02-02 1:09 ` Paolo Bonzini
2017-02-02 10:17 ` [Qemu-trivial] " Markus Armbruster
2017-02-02 10:17 ` Markus Armbruster
2017-04-21 9:08 ` [Qemu-trivial] " Peter Maydell
2017-04-21 9:08 ` Peter Maydell
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=87bmunnjd0.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=patches@linaro.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.