From: Michael Buesch <mb@bu3sch.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev 085 warnings
Date: Thu, 06 Apr 2006 00:30:41 +0000 [thread overview]
Message-ID: <200604060230.42054.mb@bu3sch.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0604051110170.11179@yvahk01.tjqt.qr>
[-- Attachment #1: Type: text/plain, Size: 1237 bytes --]
On Wednesday 05 April 2006 21:03, Kay Sievers wrote:
> On Wed, Apr 05, 2006 at 11:10:40AM +0200, Jan Engelhardt wrote:
> > I am currently compiling udev-085-14.src.rpm from the opensuse
> > OSS-factory tree on a 64-bit arch and get a lot of these warnings:
> >
> > fat.c:325: warning: cast increases required alignment of target type
> > 325:
> > next = le32_to_cpu(*((uint32_t *) buf) & 0x0fffffff);
Hm, I don't know what this code is about, but is it actually correct?
I mean, it masks the value of buf, which is appearently a little-endian
32bit value with 0x0fffffff (which is CPU order). Is that intentional?
Or should it be something like that instead:
next = le32_to_cpu(*((uint32_t *) buf)) & 0x0fffffff;
> > Will there be a proper fix or is this just another of these nice gcc
> > warnings that are superfluous?
>
> GCC is correct warning about that, cause the Makefile asked for that
> kind of warning. The buffer access is always aligned but the compiler
> can't know that. To get rid of it, you would need to memcpy() the integer
> in a variable or access it byte by byte and shift it to an integer
> value. Removing -Wcast-align should be the easiest. :)
--
Greetings Michael.
[-- Attachment #2: Type: application/pgp-signature, Size: 191 bytes --]
next prev parent reply other threads:[~2006-04-06 0:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-05 9:10 udev 085 warnings Jan Engelhardt
2006-04-05 19:03 ` Kay Sievers
2006-04-06 0:30 ` Michael Buesch [this message]
2006-04-06 2:09 ` Kay Sievers
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=200604060230.42054.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=linux-hotplug@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 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).