From: Alan Shutko <ats@acm.org>
To: root@chaos.analogic.com
Cc: Michael Meissner <meissner@spectacle-pond.org>,
Keith Owens <kaos@ocs.com.au>,
linux-kernel@vger.kernel.org
Subject: Re: sizeof problem in kernel modules
Date: Mon, 25 Jun 2001 09:59:32 -0400 [thread overview]
Message-ID: <87g0cobrgz.fsf@wesley.springies.com> (raw)
In-Reply-To: <87ofrcbryf.fsf@wesley.springies.com>
In-Reply-To: <Pine.LNX.3.95.1010625072259.5434A-100000@chaos.analogic.com> <87ofrcbryf.fsf@wesley.springies.com>
Alan Shutko <ats@acm.org> writes:
> You can look at other things too... you can memcpy structures, pass
> them into functions, call sizeof, put them in arrays... it _is_ a
> physical representation.
One more tidbit: ISO/IEC 9899:1990 3.14
3.14 object: A region of data storage in the execution environment,
the contents of which can represent values. Except for
bit-fields, objects are composed of contiguous sequences of one or
more bytes, the number, order and encoding of which are either
explicitely specified or implementation-defined.
This would specifically prohibit separating any part of a structure
from the rest.
--
Alan Shutko <ats@acm.org> - In a variety of flavors!
A king's castle is his home.
next prev parent reply other threads:[~2001-06-25 14:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-23 14:54 Der Herr Hofrat
2001-06-23 15:18 ` Keith Owens
2001-06-23 15:30 ` Russell King
2001-06-24 1:56 ` Richard B. Johnson
2001-06-24 2:12 ` Keith Owens
2001-06-24 2:43 ` Richard B. Johnson
2001-06-24 16:07 ` Lieven Marchand
2001-06-24 16:11 ` frank
2001-06-25 0:26 ` Michael Meissner
2001-06-25 11:32 ` Richard B. Johnson
2001-06-25 13:38 ` Alan Shutko
2001-06-25 14:49 ` Richard B. Johnson
2001-06-25 19:19 ` Alan Shutko
2001-06-25 13:59 ` Alan Shutko [this message]
2001-06-25 15:07 ` Andreas Schwab
2001-06-25 21:25 ` Horst von Brand
2001-06-25 20:43 ` Michael Meissner
2001-06-25 4:33 ` Anil Kumar
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=87g0cobrgz.fsf@wesley.springies.com \
--to=ats@acm.org \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=meissner@spectacle-pond.org \
--cc=root@chaos.analogic.com \
/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
all inboxes | Powered by JetHome®