All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Hopwood <david.nospam.hopwood@blueyonder.co.uk>
To: xen-devel@lists.sourceforge.net
Subject: Re: RFC: 32 bits as smallest atomic size.
Date: Sun, 27 Mar 2005 16:39:42 +0100	[thread overview]
Message-ID: <4246D3BE.3050504@blueyonder.co.uk> (raw)
In-Reply-To: <c4e23e3538e10be2da8052b736231f92@cl.cam.ac.uk>

Keir Fraser wrote:
> On 27 Mar 2005, at 00:27, David Hopwood wrote:
>> Keir Fraser wrote:
>>> On 26 Mar 2005, at 17:31, Jimi Xenidis wrote:
>>>
>>>>>> Few things to note:
>>>>>> 1) packed is [un]necessary since the ABI will do the right thing
>>>
>>> I prefer to pack things explicitly rather than rely on ABI padding.
>>
>> If you use -Wpadded when compiling with gcc then you're not relying on
>> ABI padding; you're automatically checking that it is not used. That
>> would seem to be precisely what is required here.
> 
> If I could specify it on a per-struct basis then it would be perfect.

There is no way to selectively enable/disable warnings in gcc:
<http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9049>  :-(

OTOH, spurious warnings for padding in private structures cause no real
harm. If only a few private structures are involved, you could add dummy
padding to those anyway.

-- 
David Hopwood <david.nospam.hopwood@blueyonder.co.uk>



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

  reply	other threads:[~2005-03-27 15:39 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-25 21:25 RFC: 32 bits as smallest atomic size Jimi Xenidis
2005-03-25 21:30 ` Ronald G. Minnich
2005-03-25 21:43 ` Keir Fraser
2005-03-25 23:49   ` Jimi Xenidis
2005-03-26  0:02     ` Keir Fraser
2005-03-26 14:13       ` Jimi Xenidis
2005-03-26 17:07         ` Keir Fraser
2005-03-29 20:16           ` Kurt Garloff
2005-03-26 17:36         ` Ronald G. Minnich
2005-03-26 17:29     ` Ronald G. Minnich
2005-03-26 17:31       ` Jimi Xenidis
2005-03-26 17:49         ` Keir Fraser
2005-03-26 17:56           ` Keir Fraser
2005-03-26 18:46             ` Jimi Xenidis
2005-03-27  3:34             ` Ronald G. Minnich
2005-03-27 10:56               ` Keir Fraser
2005-03-27 11:19                 ` Keir Fraser
2005-03-28 15:37                   ` Ronald G. Minnich
2005-03-28 15:34                 ` Ronald G. Minnich
2005-03-27  0:27           ` David Hopwood
2005-03-27 10:49             ` Keir Fraser
2005-03-27 15:39               ` David Hopwood [this message]
2005-03-29 21:39   ` Hollis Blanchard
  -- strict thread matches above, loose matches on Subject: below --
2005-03-29 22:00 Ian Pratt
2005-03-29 22:32 ` Hollis Blanchard
2005-03-30  3:24 ` Jimi Xenidis

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=4246D3BE.3050504@blueyonder.co.uk \
    --to=david.nospam.hopwood@blueyonder.co.uk \
    --cc=xen-devel@lists.sourceforge.net \
    /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.