public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] fat: fix unaligned errors
Date: Fri, 2 Jan 2009 17:42:04 -0500	[thread overview]
Message-ID: <200901021742.05363.vapier@gentoo.org> (raw)
In-Reply-To: <20090102222047.438838387CDB@gemini.denx.de>

On Friday 02 January 2009 17:20:47 Wolfgang Denk wrote:
> In message <vapier@gentoo.org> you wrote:
> > From: Bryan Wu <bryan.wu@analog.com>
> >
> > A couple of buffers in the fat code are declared as an array of bytes. 
> > But it is then cast up to a structure with 16bit and 32bit members. 
> > Since GCC assumes structure alignment here, we have to force the buffers
> > to be aligned according to the structure usage.
>
> ...
>
> > +__u8 get_vfatname_block[MAX_CLUSTSIZE] __attribute__
> > ((aligned(sizeof(__u16))));
>
> ...
>
> > +__u8 get_dentfromdir_block[MAX_CLUSTSIZE] __attribute__
> > ((aligned(sizeof(__u32))));
>
> ...
>
> > +__u8 do_fat_read_block[MAX_CLUSTSIZE] __attribute__
> > ((aligned(sizeof(__u32))));
>
> What makes you sure that a 16 resp. 32 bit alignment is sufficient,
> and that gcc does not decide to align such structures even stricter?

read the structures in question.  the largest member is 16bit/32bit.  i really 
dont know what other alignment gcc could randomly generate.

> Wouldn't it make more sense to use "__alignof__ ()" here to be on the
> safe side?

i found no such alignment attribute in the gcc docs which is why i suggested 
Bryan use aligned(sizeof(...)).
http://gcc.gnu.org/onlinedocs/gcc-4.3.2/gcc/Function-Attributes.html
http://gcc.gnu.org/onlinedocs/gcc-4.3.2/gcc/Variable-Attributes.html
http://gcc.gnu.org/onlinedocs/gcc-4.3.2/gcc/Type-Attributes.html
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20090102/1ce92c0d/attachment.pgp 

  reply	other threads:[~2009-01-02 22:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-02  0:54 [U-Boot] [PATCH] fat: fix unaligned errors Mike Frysinger
2009-01-02  9:32 ` Remy Bohmer
2009-01-02 10:16   ` Mike Frysinger
2009-01-02 22:20 ` Wolfgang Denk
2009-01-02 22:42   ` Mike Frysinger [this message]
2009-01-02 23:48     ` Wolfgang Denk
2009-01-03  1:47       ` Mike Frysinger
2009-01-03  1:47       ` [U-Boot] [PATCH v2] " Mike Frysinger
2009-01-24  1:03         ` Wolfgang Denk

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=200901021742.05363.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=u-boot@lists.denx.de \
    /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