All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-c-programming@vger.kernel.org
Subject: Re: newby.-interpreting C
Date: Mon, 20 Dec 2004 22:17:09 +0100	[thread overview]
Message-ID: <20041220211709.GD2460@lug-owl.de> (raw)
In-Reply-To: <cq77vi$1ej$1@sea.gmane.org>

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

On Mon, 2004-12-20 20:07:54 +0100, soraberri <421246@posta.unizar.es>
wrote in message <cq77vi$1ej$1@sea.gmane.org>:
> Hi all,
> 
> Anyone could give me the meaning of this definition? Is the 
> __attribute__ stuff what scares me. If you feel like I'm too 
> desoriented, please tell me what should I know first.
> 
> typedef struct {
> 	uint8_t b[6];
> } __attribute__((packed)) bdaddr_t;

Compilers do use __attribute__ to allow programmers to modify the
compiler's behavior in certain areas. "packed" tells the compiler to not
start each variable at a natural alignment (ie. 4 bytes on a 32bit
machine, 8 bytes on a 64bit machine). (That is, the address of a given
variable must be a multiple of 4 (or 8) bytes.)

A "packed" structure is usually used for two things:

	- In device drivers to fit a hardware device's memory-mapped
	  register structure
	- In poorly written programs to store variables into on-disk
	  files to be read back later on by other programs.

General rule: if you don't *need* this for a good reason, or if you even
don't know what it does, you don't need it, since it also introduces a
performance penalty: CPUs tend to be fast at naturally aligned memory
accesses, but quite slow on non-aligned accesses.

MfG, JBG

-- 
Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481             _ O _
"Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg  _ _ O
 fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!   O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2004-12-20 21:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-20 19:07 newby.-interpreting C soraberri
2004-12-20 19:38 ` Nir Dremer
2004-12-20 21:17 ` Jan-Benedict Glaw [this message]
2004-12-21 15:39   ` soraberri
2004-12-30 11:26   ` Glynn Clements
2004-12-30 11:40     ` Jan-Benedict Glaw

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=20041220211709.GD2460@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=linux-c-programming@vger.kernel.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.