From: Anthony Liguori <anthony@codemonkey.ws>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org, Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] [patch] add byteordered types
Date: Wed, 27 Aug 2008 12:57:19 -0500 [thread overview]
Message-ID: <48B5957F.3050000@codemonkey.ws> (raw)
In-Reply-To: <48B57EB9.2050106@redhat.com>
Gerd Hoffmann wrote:
> Anthony Liguori wrote:
>
>> Personally, I dislike the whole struct thing. I even further dislike
>> having multiple sets of conversion functions that are used in different
>> places in the code.
>>
>> Are we sure that this is something that we want to do?
>>
>
> As far I know this struct trick is the only way to have gcc check access
> to variables with an specific byteorder is done the correct way. Avi
> sguuested that and I also think this checking would be useful. I could
> live without that though if there is an agreement that we'll just stick
> with the current, unchecked cpu_to_<order><size> functions.
>
Yeah, AFAIK, it's the only way to enforce this sort of thing but it's
also ugly. If we were starting from scratch, I could see the value in
it but there's already a ton of code that's not going to be using this
mechanism that noone is going to convert. That makes me think there
isn't going to be a lot of value in it and will lead to a lot of overall
confusion.
Regards,
Anthony Liguori
> cheers,
> Gerd
>
>
>
next prev parent reply other threads:[~2008-08-27 17:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-27 11:44 [Qemu-devel] [patch] add byteordered types Gerd Hoffmann
2008-08-27 12:20 ` Paul Brook
2008-08-27 13:04 ` Gerd Hoffmann
2008-08-27 13:24 ` Gerd Hoffmann
2008-08-27 13:55 ` Paul Brook
2008-08-27 14:12 ` M. Warner Losh
2008-08-27 13:56 ` Paul Brook
2008-08-27 14:35 ` Gerd Hoffmann
2008-08-27 14:47 ` M. Warner Losh
2008-08-27 15:06 ` Gerd Hoffmann
2008-08-27 15:49 ` Anthony Liguori
2008-08-27 16:20 ` Gerd Hoffmann
2008-08-27 17:57 ` Anthony Liguori [this message]
2008-08-28 8:36 ` Gerd Hoffmann
2008-08-27 18:19 ` Jamie Lokier
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=48B5957F.3050000@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=kraxel@redhat.com \
--cc=paul@codesourcery.com \
--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).